Postgres Indexing (ADR038) Implementation

[clevinson]

Epic for tracking Postgres Indexing working group.

Design:

• ADR 038: State Listening #8012

Implementation:

• ADR-038 Part 1: WriteListener, listen.KVStore, MultiStore and KVStore updates #8551
• feat: ADR-038 Part 2: StreamingService interface, file writing implementation, and configuration #8664
• feat: ADR-038 Part 3: State change files auxiliary gRPC server #9647

[alexanderbez]

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

[aaronc]

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.

[i-norden]

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]

@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]

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

[clevinson]

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.