Re: logical decoding and replication of sequences - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: logical decoding and replication of sequences
Date
Msg-id 123965dd-d9cb-f7c8-6efa-49a10be1cb39@enterprisedb.com
Whole thread Raw
In response to Re: logical decoding and replication of sequences  (Tomas Vondra <tomas.vondra@enterprisedb.com>)
List 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.



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: pgcrypto: Remove internal padding implementation
Next
From: Yugo NAGATA
Date:
Subject: Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors