Re: protocol-level wait-for-LSN - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: protocol-level wait-for-LSN
Date
Msg-id e76f3490-5b36-457e-bb80-2a4abdba70c9@eisentraut.org
Whole thread Raw
In response to Re: protocol-level wait-for-LSN  (Tatsuo Ishii <ishii@postgresql.org>)
Responses Re: protocol-level wait-for-LSN
List pgsql-hackers
On 29.10.24 06:06, Tatsuo Ishii wrote:
>> The patch adds a protocol extension called _pq_.wait_for_lsn as well
>> as a libpq connection option wait_for_lsn to activate the same.  (Use
>> e.g., psql -d 'wait_for_lsn=1'.)
>>
>> With this protocol extension, two things are changed:
>>
>> - The ReadyForQuery message sends back the current LSN.
> 
> If other protocol extension X tries to add something to the
> ReadyForQuery message too, what would happen?

I think one would have to define that somehow.  If it's useful, the 
additional fields of both extensions could be appended, in some defined 
order.  But this is an interesting question to think about.




pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Pgoutput not capturing the generated columns
Next
From: Tender Wang
Date:
Subject: Re: Wrong result when enable_partitionwise_join is on if collation of PartitionKey and Column is different.