| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: protocol-level wait-for-LSN |
| Date: | 2024-10-29 06:28:51 |
| Message-ID: | e76f3490-5b36-457e-bb80-2a4abdba70c9@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tender Wang | 2024-10-29 06:38:30 | Re: Wrong result when enable_partitionwise_join is on if collation of PartitionKey and Column is different. |
| Previous Message | Amit Kapila | 2024-10-29 06:28:24 | Re: Pgoutput not capturing the generated columns |