| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | PFC <lists(at)peufeu(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Cached Query Plans (was: global prepared statements) |
| Date: | 2008-04-11 17:45:08 |
| Message-ID: | 13998.1207935908@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> PFC wrote:
>> So, where to go from that ? I don't see a way to implement this without
>> a (backwards-compatible) change to the wire protocol, because the clients
>> will want to specify when a plan should be cached or not. Since the user
>> should not have to name each and every one of the statements they want to
>> use plan caching, I see the following choices :
> I don't understand the point here. We already have cached plans: you
> send a Parse. You can then Bind/Execute many times.
> Maybe what we need is support for this in libpq, so that PHP can use it?
We already have that, too ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2008-04-11 17:46:18 | Re: Commit fest queue |
| Previous Message | Tom Lane | 2008-04-11 17:41:16 | Remove lossy-operator RECHECK flag? |