Re: When extended query protocol ends? - Mailing list pgsql-hackers

From Dave Cramer
Subject Re: When extended query protocol ends?
Date
Msg-id CADK3HHKQXWWP6mwErUN_3ROMDs1enmdct+KnoejO-gK7QWnCfA@mail.gmail.com
Whole thread Raw
In response to Re: When extended query protocol ends?  (Tatsuo Ishii <ishii@sraoss.co.jp>)
Responses Re: When extended query protocol ends?
List pgsql-hackers


On Wed, 14 Feb 2024 at 17:55, Tatsuo Ishii <ishii@sraoss.co.jp> wrote:
>>> From [1] I think the JDBC driver sends something like below if
>>> autosave=always option is specified.
>>>
>>> "BEGIN READ ONLY" Parse/Bind/Eexecute (in the extended query protocol)
>>> "SAVEPOINT PGJDBC_AUTOSAVE" (in the simple query protocol)
>>>
>>> It seems the SAVEPOINT is sent without finishing the extended query
>>> protocol (i.e. without Sync message). Is it possible for the JDBC
>>> driver to issue a Sync message before sending SAVEPOINT in simple
>>> query protocol? Or you can send SAVEPOINT using the extended query
>>> protocol.
>>>
>>> [1]
>>> https://www.pgpool.net/pipermail/pgpool-general/2023-December/009051.html
>>
>>
>> Can you ask the OP what version of the driver they are using. From what I
>> can tell we send BEGIN using SimpleQuery.
>
> Sure. I will get back once I get the JDBC version.

Here it is:
> JDBC driver version used:42.5.1 Regards, Karel.

Can you ask the OP what they are doing in the startup. I'm trying to replicate their situation.
Looks like possibly 'setReadOnly' and 'select version()'
 
Thanks,
Dave 

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Reducing output size of nodeToString
Next
From: Tomas Vondra
Date:
Subject: Re: index prefetching