Date: Thu, 21 Jan 2021 20:43:26 -0300
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: "David G. Johnston" <david.g.johnston@gmail.com>,
	Daniel Verite <daniel@manitou-mail.org>
Cc: Matthieu Garrigues <matthieu.garrigues@gmail.com>,
	Michael Paquier <michael@paquier.xyz>,
	Dave Cramer <davecramer@postgres.rocks>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>,
	Craig Ringer <craig@2ndquadrant.com>,
	Vaishnavi Prabakaran <vaishnaviprabakaran@gmail.com>,
	Andres Freund <andres@anarazel.de>,
	Michael Paquier <michael.paquier@gmail.com>,
	Claudio Freire <klaussfreire@gmail.com>,
	Heikki Linnakangas <heikki.linnakangas@iki.fi>
Subject: Re: PATCH: Batch/pipelining support for libpq
Message-ID: <20210121234326.GA18684@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20210121233930.GA16358@alvherre.pgsql>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

As you can see in an XXX comment in the libpq test program, the current
implementation has the behavior that PQgetResult() returns NULL after a
batch is finished and has reported PGRES_BATCH_END.  I don't know if
there's a hard reason to do that, but I'd like to supress it because it
seems weird and out of place.

-- 
Álvaro Herrera                            39°49'30"S 73°17'W