Re: 12.1 not useable: clientlib fails after a dozen queries (GSSAPI ?)

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-hackers(at)lists(dot)postgresql(dot)org, Stephen Frost <sfrost(at)snowman(dot)net>
Subject: Re: 12.1 not useable: clientlib fails after a dozen queries (GSSAPI ?)
Date: 2020-01-12 19:46:25
Message-ID: 26533.1578858385@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:
> With the first patch applied (as from Friday - applied only on the
> client side), the application did appear to work well.
> But then, when engaging bandwidth-limiting to some modem-speed, it did
> not work: psql would receive all (or most of) the data from a SELECT,
> but then somehow not recognize the end of it and sit there and wait for
> whatever:

Yeah, that's just the behavior I'd expect (and was able to reproduce
here) because of the additional design problem.

> Now with the new patches 0001+0003 applied, on both server & client,
> all now running 12.1 release, on a first run I did not perceive
> a malfunction, bandwidth limited or not.
> I'll leave them applied, but this here will not experience serious
> loads; You'll need somebody else to test for that...

Cool, let us know if you do see any problems.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message dagamier 2020-01-13 15:41:06 Re: pg_repack in cluster
Previous Message Peter 2020-01-12 18:36:33 Re: 12.1 not useable: clientlib fails after a dozen queries (GSSAPI ?)

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2020-01-12 20:59:59 Re: Consolidate 'unique array values' logic into a reusable function?
Previous Message Pavel Stehule 2020-01-12 19:11:13 Re: [Proposal] Add accumulated statistics for wait event