> On 6. Dec 2019, at 16:45, Andrew Gierth wrote:
>
>> "Jakob" == Jakob Egger writes:
>
> Jakob> But this also needs to be fixed on the client side as well,
> Jakob> otherwise affected clients can't connect to older servers
> Jakob> anymore.
>
> There's a workaround, which is to set PGGSS
> "Jakob" == Jakob Egger writes:
Jakob> But this also needs to be fixed on the client side as well,
Jakob> otherwise affected clients can't connect to older servers
Jakob> anymore.
There's a workaround, which is to set PGGSSENCMODE=disable on the
client.
It would be far better to avoid c
> On 6. Dec 2019, at 15:08, Michael Paquier wrote:
>
> On Fri, Dec 06, 2019 at 02:25:46PM +0100, Jakob Egger wrote:
>> I've received a bug report from a PostgreSQL user that psql 12.1
>> failed to connect to a PostgreSQL 12.1 server, with the following
>> error message:
>>
>> psql: error: cou
On Fri, Dec 06, 2019 at 02:25:46PM +0100, Jakob Egger wrote:
> I've received a bug report from a PostgreSQL user that psql 12.1
> failed to connect to a PostgreSQL 12.1 server, with the following
> error message:
>
> psql: error: could not connect to server: FATAL: unsupported
> frontend protocol
Hi!
I've received a bug report from a PostgreSQL user that psql 12.1 failed to
connect to a PostgreSQL 12.1 server, with the following error message:
psql: error: could not connect to server: FATAL: unsupported frontend protocol
1234.5679: server supports 2.0 to 3.0
After inspecting a TCP dump
