From: | Peter <pmc(at)citylink(dot)dinoex(dot)sub(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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 20:53:19 |
Message-ID: | 20200109205319.GA85142@gate.oper.dinoex.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Thu, Jan 09, 2020 at 01:48:01PM -0500, Tom Lane wrote:
! Peter <pmc(at)citylink(dot)dinoex(dot)sub(dot)org> writes:
! > with 12.1, after a couple of queries, at a random place, the clientlib
! > does produce a failed query without giving reason or error-message [1].
! > Then when retrying, the clientlib switches off signal handling and
! > sits inactive in memory (needs kill -9).
!
! Seems like you'd better raise this with the author(s) of the "pg"
! Ruby gem. Perhaps they read this mailing list, but more likely
! they have a specific bug reporting mechanism somewhere.
Tom,
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
message type 0x44 arrived from server while idle
message type 0x44 arrived from server while idle
message type 0x44 arrived from server while idle
message type 0x44 arrived from server while idle
message type 0x44 arrived from server while idle
message type 0x44 arrived from server while idle
message type 0x44 arrived from server while idle
message type 0x44 arrived from server while idle
message type 0x44 arrived from server while idle
message type 0x44 arrived from server while idle
message type 0x44 arrived from server while idle
message type 0x44 arrived from server while idle
message type 0x44 arrived from server while idle
message type 0x44 arrived from server while idle
flowmdev=> select * from flows;
server sent data ("D" message) without prior row description ("T" message)
flowmdev=> select * from flows;
message type 0x54 arrived from server while idle
message type 0x44 arrived from server while idle
message type 0x44 arrived from server while idle
message type 0x44 arrived from server while idle
message type 0x44 arrived from server while idle
message type 0x44 arrived from server while idle
message type 0x44 arrived from server while idle
id | name | ... <here finally starts the data as expected>
To the contrary:
$ PGGSSENCMODE="disable" psql -h myhost flowmdev
psql (12.1)
Type "help" for help.
flowmdev=> select * from flows;
id | name | ... <all working as normal>
rgds,
PMc
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-01-09 21:27:06 | Re: INSERT locking order |
Previous Message | Peter | 2020-01-09 20:53:17 | Re: 12.1 not useable: clientlib fails after a dozen queries (GSSAPI ?) |
From | Date | Subject | |
---|---|---|---|
Next Message | David Kimura | 2020-01-09 20:55:03 | Re: Make autovacuum sort tables in descending order of xid_age |
Previous Message | Peter | 2020-01-09 20:53:17 | Re: 12.1 not useable: clientlib fails after a dozen queries (GSSAPI ?) |