Re: libpq support for NegotiateProtocolVersion

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Jacob Champion <jchampion(at)timescale(dot)com>
Cc: Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: libpq support for NegotiateProtocolVersion
Date: 2022-11-17 15:00:11
Message-ID: 1a280569-6900-f62d-af34-74d4c457ae5a@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 16.11.22 19:35, Jacob Champion wrote:
> On Tue, Nov 15, 2022 at 2:19 AM Peter Eisentraut
> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>> I think for the current code, the following would be an appropriate
>> adjustment:
>>
>> diff --git a/src/interfaces/libpq/fe-connect.c
>> b/src/interfaces/libpq/fe-connect.c
>> index 746e9b4f1efc..d15fb96572d9 100644
>> --- a/src/interfaces/libpq/fe-connect.c
>> +++ b/src/interfaces/libpq/fe-connect.c
>> @@ -3412,8 +3412,7 @@ PQconnectPoll(PGconn *conn)
>> /* Get the type of request. */
>> if (pqGetInt((int *) &areq, 4, conn))
>> {
>> - /* We'll come back when there are more data */
>> - return PGRES_POLLING_READING;
>> + goto error_return;
>> }
>> msgLength -= 4;
>>
>> And then the handling of the 'v' message in my patch would also be
>> adjusted like that.
>
> Yes -- though that particular example may be dead code, since we
> should have already checked that there are at least four more bytes in
> the buffer.

I have committed this change and the adjusted original patch. Thanks.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Japin Li 2022-11-17 15:06:22 Re: redundant check of msg in does_not_exist_skipping
Previous Message Andrew Dunstan 2022-11-17 14:58:48 Re: allow segment size to be set to < 1GiB