Re: A modest proposal: make parser/rewriter/planner inputs read-only

From: Andrei Lepikhov <lepihov(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: A modest proposal: make parser/rewriter/planner inputs read-only
Date: 2025-04-16 18:07:45
Message-ID: b0d4ad4a-31b5-433f-8d1a-7ff520bec62e@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 4/16/25 18:22, Tom Lane wrote:
> Maybe we would like to have some enforced contract about what
> subquery_planner can and can't touch in the outer planner level's
> data, but I'm not feeling a great need for that right now.
I wouldn't say I'm entirely convinced that side effects are absent, but
multiple copies of the same query tree look messy now. It makes sense to
try this way and see what happens.

--
regards, Andrei Lepikhov

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Renan Alves Fonseca 2025-04-16 18:38:54 Prototype: Implement dead tuples xid histograms
Previous Message Alexander Lakhin 2025-04-16 18:00:00 Re: recoveryCheck test failure on flaviventris