Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Ã?lvaro Herrera <alvherre(at)kurilemu(dot)de>, exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
Date: 2025-07-16 04:45:55
Message-ID: aHcug1wt_RvLwWV4@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Jul 15, 2025 at 07:40:19PM -0400, Tom Lane wrote:
> Michael Paquier <michael(at)paquier(dot)xyz> writes:
>> 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.

Oh, OK, I was not sure about your point here. Thanks for clarifying.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Yaroslav Syrytsia 2025-07-16 09:33:33 Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution
Previous Message Michael Paquier 2025-07-16 00:10:36 Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution