From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter <pmc(at)citylink(dot)dinoex(dot)sub(dot)org> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: 12.1 not useable: clientlib fails after a dozen queries (GSSAPI ?) |
Date: | 2020-01-09 21:31:44 |
Message-ID: | 15232.1578605504@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Peter <pmc(at)citylink(dot)dinoex(dot)sub(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2020-01-10 00:11:24 | Re: what to do after a failover |
Previous Message | Tom Lane | 2020-01-09 21:27:06 | Re: INSERT locking order |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2020-01-09 21:38:42 | Re: Allow 'sslkey' and 'sslcert' in postgres_fdw user mappings |
Previous Message | Tom Lane | 2020-01-09 20:58:26 | Re: Coding in WalSndWaitForWal |