Re: logical decoding and replication of sequences

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Petr Jelinek <petr(dot)jelinek(at)enterprisedb(dot)com>
Subject: Re: logical decoding and replication of sequences
Date: 2022-03-22 08:09:16
Message-ID: 123965dd-d9cb-f7c8-6efa-49a10be1cb39@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Yugo NAGATA 2022-03-22 08:27:14 Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors
Previous Message Peter Eisentraut 2022-03-22 08:01:09 Re: pgcrypto: Remove internal padding implementation