From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
---|---|
To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: Transient plans versus the SPI API |
Date: | 2011-08-06 20:24:39 |
Message-ID: | m2y5z6i8zc.fsf@2ndQuadrant.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jeff Davis <pgsql(at)j-davis(dot)com> writes:
> A control knob sounds limited. For instance, what if the application
> knows that some parameters will be constant over the time that the plan
> is saved? It would be nice to be able to bind some parameters to come up
> with a generic (but less generic) plan, and then execute it many times.
> Right now that can only be done by inlining such constants in the SQL,
> which is what we want to avoid.
+1
I was already thinking in those term at the application level for the
example I've been using before in this thread, and only reading your
mail I realize that maybe the backend should be able to do that itself.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Kupershmidt | 2011-08-07 01:57:47 | Re: vacuumlo patch |
Previous Message | Tom Lane | 2011-08-06 19:30:30 | Re: mosbench revisited |