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

Support replication #522

Open
pnewell opened this issue Nov 24, 2024 · 1 comment
Open

Support replication #522

pnewell opened this issue Nov 24, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@pnewell
Copy link

pnewell commented Nov 24, 2024

Please summarize your feature request

Using with Postgres logical replication to get a stream of changes to the database

Describe the functionality you're seeking in more detail

I'd like to use postgres-nio to work with logical replication but it looks like for now messages related to it are marked precondition failures. It looks like a lot of the functionality in the New folder is moving towards making messages, etc internal, which may mean trying to extend things to intercept and process these messages myself won't be possible. Is there any recommended way I could do this while still using postgres-nio as a base? Or is the only option to fork/wait for it to be implemented given the direction the library is headed?

Have you considered any alternatives?

I've started to work through forking but would rather avoid that if possible

@pnewell pnewell added the enhancement New feature or request label Nov 24, 2024
@fabianfett
Copy link
Collaborator

As replication likely requires different state machines, I'm pretty confident that forking is the best option right now. We might want to consider putting the messages into an extra target, that you could depend upon. Not sure if there is much more reusable besides the message definitions.

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

No branches or pull requests

2 participants