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-06 01:09:18 |
Message-ID: | 2717930.1733447358@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I wrote:
> Don't like this much. I'm not sure I believe any part of this
> approach to deciding whether the portal is "run once". In any
> case, a proper fix for this needs to include actually documenting
> what that field means and does.
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.)
regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
v1-remove-run_once-execute_once-flags.patch | text/x-diff | 16.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | jian he | 2024-12-06 02:22:14 | Re: attndims, typndims still not enforced, but make the value within a sane threshold |
Previous Message | Joseph Koshakow | 2024-12-06 01:00:12 | Re: Remove dependence on integer wrapping |