Re: Deparsing rewritten query
| От | Tom Lane |
|---|---|
| Тема | Re: Deparsing rewritten query |
| Дата | |
| Msg-id | 8085.1624806845@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: Deparsing rewritten query (Julien Rouhaud <rjuju123@gmail.com>) |
| Ответы |
Re: Deparsing rewritten query
Re: Deparsing rewritten query |
| Список | pgsql-hackers |
Julien Rouhaud <rjuju123@gmail.com> writes:
> On Sun, Jun 27, 2021 at 10:34:52AM -0400, Tom Lane wrote:
>> It's not very hard to imagine someday moving view
>> expansion into the planner on efficiency grounds, leaving the rewriter
>> handling only the rare uses of INSERT/UPDATE/DELETE rules.
> Agreed. One the other hand having such a function in core may ensure that any
> significant change in those area will keep an API to retrieve the final query
> representation.
My point is precisely that I'm unwilling to make such a promise.
I do not buy that this capability is worth very much, given that
we've gotten along fine without it for twenty-plus years. If you
want to have it as an internal, might-change-at-any-time API,
that seems all right. If you're trying to lock it down as something
that will be there forevermore, you're likely to end up with nothing.
regards, tom lane
В списке pgsql-hackers по дате отправления: