Re: Assert failure on running a completed portal again

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Assert failure on running a completed portal again
Date: 2024-12-08 19:25:53
Message-ID: 3704565.1733685953@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> After looking at this further, I think this whole "run_once"
> business is badly designed, worse documented, and redundant
> (as well as buggy). It can be replaced with three self-contained
> lines in ExecutePlan, as per the attached.

> (Obviously, the API changes in this wouldn't do for the back
> branches. But we could leave those arguments in place as
> unused dummies.)

Here's a cut-down version that I think would be OK to use in the
back branches.

regards, tom lane

Attachment Content-Type Size
v1-remove-run_once-execute_once-flags-v17.patch text/x-diff 6.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jelte Fennema-Nio 2024-12-08 22:08:47 Re: Add a warning message when using unencrypted passwords
Previous Message Tomas Vondra 2024-12-08 18:48:38 Re: Trim the heap free memory