From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter <pmc@citylink.dinoex.sub.org>
cc: pgsql-general@lists.postgresql.org
Subject: Re: 12.1 not useable: clientlib fails after a dozen queries (GSSAPI
 ?)
In-reply-to: <20200109205319.GA85142@gate.oper.dinoex.org>
References: <20200109181822.GA74698@gate.oper.dinoex.org>
 <7042.1578595681@sss.pgh.pa.us> <20200109205319.GA85142@gate.oper.dinoex.org>
Comments: In-reply-to Peter <pmc@citylink.dinoex.sub.org>
	message dated "Thu, 09 Jan 2020 21:53:19 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <15231.1578605504.1@sss.pgh.pa.us>
Date: Thu, 09 Jan 2020 16:31:44 -0500
Message-ID: <15232.1578605504@sss.pgh.pa.us>
Precedence: bulk

Peter <pmc@citylink.dinoex.sub.org> writes:
>  I don't think this has anything to do with "pg". Just checked: I get
> garbage and misbehaviour on the "psql" command line tool also:

> $ psql -h myhost flowmdev
> psql (12.1)
> GSSAPI-encrypted connection
> Type "help" for help.

> flowmdev=> select * from flows;
> message type 0x44 arrived from server while idle
> message type 0x44 arrived from server while idle
> message type 0x44 arrived from server while idle

Oh ... that does look pretty broken.  However, we've had no other similar
reports, so there must be something unique to your configuration.  Busted
GSSAPI library, or some ABI inconsistency, perhaps?  What platform are you
on, and how did you build or obtain this Postgres code?

			regards, tom lane