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 ) id 1ubpG7-005kxd-GF for pgsql-bugs@arkaria.postgresql.org; Tue, 15 Jul 2025 23:40:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1ubpG5-006OLQ-IJ for pgsql-bugs@arkaria.postgresql.org; Tue, 15 Jul 2025 23:40:26 +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 ) id 1ubpG5-006OLG-A3 for pgsql-bugs@lists.postgresql.org; Tue, 15 Jul 2025 23:40:25 +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.96) (envelope-from ) id 1ubpG3-007xcX-2S for pgsql-bugs@lists.postgresql.org; Tue, 15 Jul 2025 23:40:25 +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 56FNeJYC1143241; Tue, 15 Jul 2025 19:40:19 -0400 From: Tom Lane To: Michael Paquier cc: =?iso-8859-1?Q?=C3=3Flvaro?= Herrera , exclusion@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti In-reply-to: References: <18984-0f4778a6599ac3ae@postgresql.org> <715434.1752521761@sss.pgh.pa.us> <799185.1752535067@sss.pgh.pa.us> <923531.1752595534@sss.pgh.pa.us> Comments: In-reply-to Michael Paquier message dated "Wed, 16 Jul 2025 08:32:00 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1143239.1752622819.1@sss.pgh.pa.us> Date: Tue, 15 Jul 2025 19:40:19 -0400 Message-ID: <1143240.1752622819@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Michael Paquier writes: > On Tue, Jul 15, 2025 at 12:05:34PM -0400, Tom Lane wrote: >> Perhaps we should >> add something about the possibility that an outer Portal level >> can supply a default command tag if we lack one now? > You mean as an extra assertion? I am not sure that this is strongly > necessary but why not. No, I meant that the comment could explain that if we fail to assign a non-unknown CMDTAG here, there's still a possibility of an outer Portal level supplying one. But I don't see how to make a useful assertion about that. regards, tom lane