Logical Replication Support #339
Closed
Conversation
This file contains 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
|
I agree to the changes to |
|
Yeah, I was leaning towards removing it before I submitted the PR. The code was just there since that was my end goal and what I wanted tested. I just removed it. Thank you! |
|
I merged this. Thank you! |
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.
I'm currently building a data streaming system and would like to use the streaming replication protocol.
The biggest change would be the addition of
PGRES_COPY_BOTHin thepgconn_get_last_resultfunction, marking it as an empty result. Otherwise fetching a result would never return since it would be expecting a result to come in.The
PG::LogicalReplicationmay not be the best spot for this code and am happy to take it out.