Re: Cached Query Plans (was: global prepared statements)

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: PFC <lists(at)peufeu(dot)com>
Cc: "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:06:09
Message-ID: 20080411170609.GB4392@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Rick Gigger 2008-04-11 17:08:32 Re: Commit fest queue
Previous Message Teodor Sigaev 2008-04-11 16:48:24 Re: Index AM change proposals, redux