Re: Fatel: unsupported frientend protocol error

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, eswar reddy <eswarareddyps03(at)gmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Fatel: unsupported frientend protocol error
Date: 2022-06-30 13:27:04
Message-ID: 4080766.1656595624@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Thursday, June 30, 2022, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
>> On Thu, 2022-06-30 at 16:40 +0530, eswar reddy wrote:
>>> Fatel: unsupported frientend protocol 1234.5680: server supports 1.0 to
>>> 3.0

>> This is simple: upgrade the server to a supported version, ideally v14.

> Good advice regardless, but wouldn’t v14 still give that same error if some
> client tried to present protocol version 1234.5680 as the desired
> communicarion protocol?

Per src/include/libpq/pqcomm.h, that code is

#define NEGOTIATE_GSS_CODE PG_PROTOCOL(1234,5680)

So some client is running code new enough to try GSS protocol,
but the 9.6 server doesn't know what that is. You'd need v12
or later server if you don't want to see these complaints.
(But you could just ignore them.)

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2022-06-30 14:40:13 Re: Function inside query status
Previous Message Aleš Zelený 2022-06-30 12:44:34 pg_amcheck warnings after upgrade to 14.4