Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Postgres Indexing (ADR038) Implementation #9817

Closed
2 of 4 tasks
clevinson opened this issue Jul 29, 2021 · 6 comments
Closed
2 of 4 tasks

Postgres Indexing (ADR038) Implementation #9817

clevinson opened this issue Jul 29, 2021 · 6 comments

Comments

@clevinson
Copy link
Contributor

clevinson commented Jul 29, 2021

@clevinson clevinson added the Epic label Jul 29, 2021
@alexanderbez
Copy link
Contributor

Note, Tendermint already supports indexing all block and transaction events. Is this issue meant to track relational data indexing of state writes?

@aaronc
Copy link
Member

aaronc commented Jul 30, 2021

Note, Tendermint already supports indexing all block and transaction events. Is this issue meant to track relational data indexing of state writes?

Yes, it's related to ADR 38 which has been in progress for a while. We should have more info in these epic descriptions.

@clevinson clevinson changed the title Postgres Indexing Postgres Indexing (ADR038) Implementation Aug 6, 2021
@clevinson clevinson added this to the v0.45 milestone Aug 6, 2021
@i-norden
Copy link
Contributor

We also want to track those state changes in relation to the Tendermint txs/abci requests that cause them and the abci responses they cause.

@i-norden
Copy link
Contributor

@clevinson I created this issue, which is a bit of a duplication of this one but contains additional/updated information: #10096. I think we should either copy the content there over to the top-level comment here or close this and use that issue for tracking ADR-038 going forward.

@tac0turtle
Copy link
Member

On todays, cosmos-sdk call we discussed getting this in for 0.45. @i-norden does this sound reasonable for you?

@clevinson
Copy link
Contributor Author

Closing this issue in favor of #10096, so @i-norden can manage the description / items in the issue.

@marbar3778 I'll relay our comment over there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants