Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-sql-owner+archive@lists.postgresql.org>)
	id 1rkGef-00Bamq-VZ
	for pgsql-sql@arkaria.postgresql.org; Wed, 13 Mar 2024 04:55:54 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-sql-owner+archive@lists.postgresql.org>)
	id 1rkGee-00AaWJ-0h
	for pgsql-sql@arkaria.postgresql.org; Wed, 13 Mar 2024 04:55:52 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1rkGed-00AaWA-OD
	for pgsql-sql@lists.postgresql.org; Wed, 13 Mar 2024 04:55:52 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by magus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1rkGeb-004EtM-GZ
	for pgsql-sql@lists.postgresql.org; Wed, 13 Mar 2024 04:55:51 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 42D4tli81982249;
	Wed, 13 Mar 2024 00:55:47 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Evgeny Smirnov <evgeny.v.smirnov@gmail.com>
cc: pgsql-sql@lists.postgresql.org
Subject: Re: Can portals interleave with other portals
In-reply-to: 
 <CAB9opTGs-Aa9aQf9kM0xpZHOcGVAeR1rLLkNbH8A-HKD0WJ54w@mail.gmail.com>
References: 
 <CAB9opTGs-Aa9aQf9kM0xpZHOcGVAeR1rLLkNbH8A-HKD0WJ54w@mail.gmail.com>
Comments: In-reply-to Evgeny Smirnov <evgeny.v.smirnov@gmail.com>
	message dated "Wed, 13 Mar 2024 11:38:09 +0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1982247.1710305747.1@sss.pgh.pa.us>
Date: Wed, 13 Mar 2024 00:55:47 -0400
Message-ID: <1982248.1710305747@sss.pgh.pa.us>
List-Id: <pgsql-sql.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-sql@lists.postgresql.org>
List-Owner: <mailto:pgsql-sql-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-sql>
Archived-At: 
 <https://www.postgresql.org/message-id/1982248.1710305747%40sss.pgh.pa.us>
Precedence: bulk

Evgeny Smirnov <evgeny.v.smirnov@gmail.com> writes:
> A Postgresql backend is capable of operating multiple portals within a
> transaction and switching between them on and off. For instance such a code
> results in an expected outcome:
> ...
> Is the same possible for conventional selects issued with extended query
> protocol?

AFAIR, a portal is a portal.  Have you tried it?  If it didn't do
what you expected, please provide a less handwavy example.

			regards, tom lane