Avoid 'interleaved LSN' in postgres replication slot

Asked Jan 13 '23 at 14:51

Active Jan 14 '23 at 05:28

Viewed 94 times

I am trying to stream data from postgres replication slot with output plugin 'test_decoding'. When there are big, multiple transactions running, the output plugin seems to have interleaved LSN, ie, they are not in sequence.

How can I have the transactions in sequence and if that's not possible, how can I keep track of the offset, ie, up till where I have read and I will use this offset as starting point to stream data.

edited Jan 14 '23 at 05:28

asked Jan 13 '23 at 14:51

Adrij Shikhar

Why would you need that? – Laurenz Albe Jan 13 '23 at 15:16
1

Can you give a concrete example of what you mean? Maybe using `pg_recvlogical -v` to test it. – jjanes Jan 13 '23 at 16:26
@LaurenzAlbe I need this because I am working on a generic app to replicate data from any postgres source – Adrij Shikhar Jan 14 '23 at 05:30
Yes, but why is a certain sequence of log sequence numbers important for you? – Laurenz Albe Jan 14 '23 at 18:21
@LaurenzAlbe I will be storing the offset up till where I have read from the slot and the next time, I stream, I will use this offset as starting point – Adrij Shikhar Jan 16 '23 at 11:30

Avoid 'interleaved LSN' in postgres replication slot

0 Answers0