You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: