Re: logical decoding and replication of sequences

Peter Eisentraut <peter.eisentraut@enterprisedb.com>

From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: Amit Kapila <amit.kapila16@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Petr Jelinek <petr.jelinek@enterprisedb.com>
Date: 2022-03-22T08:09:16Z
Lists: pgsql-hackers
On 21.03.22 22:54, Tomas Vondra wrote:
> On 3/21/22 14:05, Peter Eisentraut wrote:
>> On 20.03.22 23:55, Tomas Vondra wrote:
>>> Attached is a rebased patch, addressing most of the remaining issues.
>>
>> This looks okay to me, if the two FIXMEs are addressed.  Remember to
>> also update protocol.sgml if you change LOGICAL_REP_MSG_SEQUENCE.
> 
> Thanks. Do we want to use a different constant for the sequence message?
> I've used 'X' for the WIP patch, but maybe there's a better value?

I would do small 's'.  Alternatively, 'Q'/'q' is still available, too.



Commits

  1. Fix cache invalidation bug in recovery_prefetch.

  2. Revert "Logical decoding of sequences"

  3. Minor improvements in sequence decoding code and docs

  4. Handle sequences in preprocess_pubobj_list

  5. Update tab-completion for CREATE PUBLICATION with sequences

  6. Add decoding of sequences to built-in replication

  7. Stabilize test_decoding touching with sequences

  8. Call ReorderBufferProcessXid from sequence_decode

  9. Add decoding of sequences to test_decoding

  10. Replace Test::More plans with done_testing

  11. Logical decoding of sequences

  12. Respect permissions within logical replication.