Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1ePM7h-0007VI-7M
	for pgsql-docs@arkaria.postgresql.org; Thu, 14 Dec 2017 05:31:57 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1ePM7g-0000qD-Jo
	for pgsql-docs@arkaria.postgresql.org; Thu, 14 Dec 2017 05:31:56 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <a.sher@postgrespro.ru>)
	id 1ePM7g-0000q2-6u
	for pgsql-docs@lists.postgresql.org; Thu, 14 Dec 2017 05:31:56 +0000
Received: from mail.postgrespro.ru ([93.174.131.138])
	by magus.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <a.sher@postgrespro.ru>)
	id 1ePM7Z-0002fN-39
	for pgsql-docs@postgresql.org; Thu, 14 Dec 2017 05:31:55 +0000
Received: from localhost (localhost [127.0.0.1])
	by mail.postgrespro.ru (Postfix) with ESMTP id 7111621C1FEB;
	Thu, 14 Dec 2017 08:31:46 +0300 (MSK)
X-Virus-Scanned: Debian amavisd-new at postgrespro.ru
Received: from ars-thinkpad (gw.postgrespro.ru [93.174.131.141])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client did not present a certificate)
	by mail.postgrespro.ru (Postfix) with ESMTPSA id 2ED7821C04B6;
	Thu, 14 Dec 2017 08:31:46 +0300 (MSK)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru;
	s=mail; t=1513229506;
	bh=LkHWWAM/o9QZ0H15+hewCIR1NryV9faACju38m3+OZA=;
	h=From:To:Cc:Subject:References:Date:In-Reply-To;
	b=RDaU99lrbNTK1waeypzQpA0ypcJWapf1tObh98nrV3EB4E7MxyMPupNoIhMrGo80q
	 YssVB8uCNulVB6xawg8PHB9Zz0a7aVNkQftt44rXlkUXncm4cFRJmGcqrFgUdzDH96
	 jJ/5DH3Aw7LffQIufm+yI+yX3/HtXGwH7Hzph4hM=
From: Arseny Sher <a.sher@postgrespro.ru>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-docs@postgresql.org
Subject: Re: Is PQgetResult() guaranteed to return the whole SQL command
 result?
References: <87o9n2hh30.fsf@ars-thinkpad>
	<f2f8adbf-d6e9-4e49-06b6-d1765a101ccf@2ndquadrant.com>
Date: Thu, 14 Dec 2017 08:31:45 +0300
In-Reply-To: <f2f8adbf-d6e9-4e49-06b6-d1765a101ccf@2ndquadrant.com> (Peter
	Eisentraut's message of "Wed, 13 Dec 2017 12:20:33 -0500")
Message-ID: <87h8stho3i.fsf@ars-thinkpad>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
List-Id: <pgsql-docs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-docs@lists.postgresql.org>
List-Owner: <mailto:pgsql-docs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-docs>
Precedence: bulk

Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:

> Are you asking whether it is possible that the results for the two
> statements might be split across more than two libpq result sets?
> That is not possible.

Yes, that was the question. Thanks!

--
Arseny Sher
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company