From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter <pmc@citylink.dinoex.sub.org>
cc: pgsql-hackers@lists.postgresql.org, Stephen Frost <sfrost@snowman.net>
Subject: Re: 12.1 not useable: clientlib fails after a dozen queries (GSSAPI
 ?)
In-reply-to: <20200112183633.GA93629@gate.oper.dinoex.org>
References: <20200109181822.GA74698@gate.oper.dinoex.org>
 <7042.1578595681@sss.pgh.pa.us> <20200109205319.GA85142@gate.oper.dinoex.org>
 <15232.1578605504@sss.pgh.pa.us>
 <20200110022342.GA92515@gate.oper.dinoex.org>
 <12348.1578679149@sss.pgh.pa.us> <20200110210337.GA9580@gate.oper.dinoex.org>
 <26433.1578714710@sss.pgh.pa.us>
 <20200112183633.GA93629@gate.oper.dinoex.org>
Comments: In-reply-to Peter <pmc@citylink.dinoex.sub.org>
	message dated "Sun, 12 Jan 2020 19:36:33 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <26532.1578858385.1@sss.pgh.pa.us>
Date: Sun, 12 Jan 2020 14:46:25 -0500
Message-ID: <26533.1578858385@sss.pgh.pa.us>
Precedence: bulk

Peter <pmc@citylink.dinoex.sub.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