Re: Transient plans versus the SPI API

From: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
To: Hannu Krosing <hannu(at)krosing(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Transient plans versus the SPI API
Date: 2011-08-11 17:56:29
Message-ID: m262m3de7m.fsf@2ndQuadrant.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hannu Krosing <hannu(at)krosing(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2011-08-11 18:25:43 Re: Extra check in 9.0 exclusion constraint unintended consequences
Previous Message Tom Lane 2011-08-11 17:50:02 Re: small issue with host names in hba