Use a shared ChainHeadUpdateListener to avoid too many Postgres connections
#891
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ghost
added
the
Jannis
force-pushed
the
jannis/shared-chain-head-update-listener
branch
3 times, most recently
from
9e8790e to
43dc61b
Compare
This fixes #889 by using a single Postgres connection for the chain head update streams of all subgraph deployments.
Jannis
force-pushed
the
jannis/shared-chain-head-update-listener
branch
from
43dc61b to
9be1279
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes #889 by using a single Postgres connection for the chain
head update streams of all subgraph deployments.