Skip to content

Grouping at replicator and restart case #58

Answered by shayonj
Manju050 asked this question in Q&A
Discussion options

You must be logged in to vote

Heya!

For 1&2: Because we use postgres' logical replication, combined with replication slot, pg_flo only sees committed transactions. The operations are then sent in order to NATS. From there the worker also pulls them in order, applies any transformation or rules and then syncs to the appropriate, all in the same order. If a transaction wasn't committed in postgres or rolled back, pg_flo won't see that. Also, for related reasons, it's recommended to only have one worker for now - https://github.com/pgflo/pg_flo?tab=readme-ov-file#scaling-guide. It can be 5-8k ops/s.

For 3: Thats right, one group is basically equivalent of one Publication and replication. Its basically a grouping of all t…

Replies: 1 comment 26 replies

Comment options

You must be logged in to vote
26 replies
@shayonj
Comment options

@Manju050
Comment options

@shayonj
Comment options

@Manju050
Comment options

@Manju050
Comment options

Answer selected by shayonj
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants