public inbox for [email protected]  

help / color / mirror / Atom feed

From: Peter Eisentraut <[email protected]>
To: Tatsuo Ishii <[email protected]>
Cc: [email protected]
Subject: Re: protocol-level wait-for-LSN
Date: Tue, 29 Oct 2024 07:28:51 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

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.

view thread (8+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: protocol-level wait-for-LSN
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox