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

Поиск
Список
Период
Сортировка
От Andrei Lepikhov
Тема Re: A modest proposal: make parser/rewriter/planner inputs read-only
Дата
Msg-id 75a742bc-151e-4286-a2cc-01d0c26c1ffd@gmail.com
обсуждение исходный текст
Ответ на Re: A modest proposal: make parser/rewriter/planner inputs read-only  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: A modest proposal: make parser/rewriter/planner inputs read-only
Список pgsql-hackers
On 4/15/25 19:34, Tom Lane wrote:
> 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?
I just want to understand how your idea will work. The query_planner 
does the job for subqueries separately. If a query is transformed in 
some way (let's say, an unnecessary join is deleted), we need to change 
references in the parse tree of another subquery, or it will not find 
the reference at the moment of planning, right?

-- 
regards, Andrei Lepikhov



В списке pgsql-hackers по дате отправления: