Re: Transient plans versus the SPI API
| От | Dimitri Fontaine |
|---|---|
| Тема | Re: Transient plans versus the SPI API |
| Дата | |
| Msg-id | m262m3de7m.fsf@2ndQuadrant.fr обсуждение исходный текст |
| Ответ на | Re: Transient plans versus the SPI API (Hannu Krosing <hannu@krosing.net>) |
| Список | pgsql-hackers |
Hannu Krosing <hannu@krosing.net> writes: >> Hm, you mean reverse-engineering the parameterization of the query? > > Yes, basically re-generate the query after (or while) parsing, replacing > constants and arguments with another set of generated arguments and > printing the list of these arguments at the end. It may be easiest to do > This in parallel with parsing. > >> Interesting thought, but I really don't see a way to make it practical. > > Another place where this could be really useful is logging & monitoring Another big use case is full support for materialized views: we could then optimize a query to automatically use a matview even when written against the “usual” schema. Now matviews are another kind of indexes. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
В списке pgsql-hackers по дате отправления: