Re: protocol-level wait-for-LSN

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: peter(at)eisentraut(dot)org
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: protocol-level wait-for-LSN
Date: 2024-10-30 06:49:19
Message-ID: 20241030.154919.859856957033404666.ishii@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>> 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.

I think this kind of extension, which adds new filed to an existing
message type, should be implemented as v4 protocol.

Best reagards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Yushi Ogiwara 2024-10-30 07:00:52 Re: Fix for consume_xids advancing XIDs incorrectly
Previous Message Hunaid Sohail 2024-10-30 06:07:27 Re: Psql meta-command conninfo+