| From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: ERROR: too late to create a new PlaceHolderInfo |
| Date: | 2026-11-06 01:11:16 |
| Message-ID: | CAMbWs49329Ak1X8Yr1+mSTmcc6xGcZuUwrMM4gsVvprG9m6ckQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 5, 2026 at 5:29 PM Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
> Given the wrong results, I think we need to reconsider back-patching
> to v16. Is fixing this in the back branches worth the risk of an ABI
> break?
I searched some open-source extensions and found several that allocate
their own PlannerInfo, such as TimescaleDB, HypoPG and pg_ivm, and
Apache AGE even passes one to flatten_join_alias_vars. This close to
the minor releases, I didn't want to risk an ABI break, so I've pushed
it to master and v19 only.
(v16-v18 still give these wrong results silently, but I don't know
what to do about them for now.)
- Richard
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yilin Zhang | 2026-11-06 01:17:12 | Re: Fix stale column context after COPY FROM conversion errors |
| Previous Message | Baji Shaik | 2026-11-05 23:52:12 | Fix pg_dump of grouped large object ACLs granted by a non-owner |