Re: A modest proposal: make parser/rewriter/planner inputs read-only - Mailing list pgsql-hackers

From Tom Lane
Subject Re: A modest proposal: make parser/rewriter/planner inputs read-only
Date
Msg-id 1705756.1744738495@sss.pgh.pa.us
Whole thread Raw
In response to Re: A modest proposal: make parser/rewriter/planner inputs read-only  (Andrei Lepikhov <lepihov@gmail.com>)
Responses Re: A modest proposal: make parser/rewriter/planner inputs read-only
List pgsql-hackers
Andrei Lepikhov <lepihov@gmail.com> writes:
> But what is the way you are proposing here? Do you mean that one more 
> entity will be explicitly introduced: a transformed parse tree?

No, I wasn't thinking of adding new concepts, just saying that the
inputs to certain operations need to be treated as read-only.
What would you envision a "transformed parse tree" being that's not
what we have today?

> It would open an opportunity for extensions to build a set of 
> alternative transformed trees, pass them through the optimisation phase 
> and choose the best plan.

Yeah, the ability to repeatedly operate on a tree without the overhead
of making copies would be a major benefit of being stricter here.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: A modest proposal: make parser/rewriter/planner inputs read-only
Next
From: Jacob Champion
Date:
Subject: Re: [PoC] Federated Authn/z with OAUTHBEARER