Re: Admission Control Policy

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Dimitri Fontaine" <dfontaine(at)hi-media(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Admission Control Policy
Date: 2009-12-28 22:56:34
Message-ID: 4B38E343020000250002D9C7@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dimitri Fontaine <dfontaine(at)hi-media(dot)com> wrote:
> Le 28 déc. 2009 à 22:59, Kevin Grittner a écrit :

>> (3) With the ACP, the statements would be parsed and optimized
>> before queuing, so they would be "ready to execute" as soon as a
>> connection was freed.
>
> There's a pgfoundry project called preprepare, which can be used
> along with pgbouncer to get this effect. If you use 8.4, you can
> even get the effect without pgbouncer.
>
> http://preprepare.projects.postgresql.org/README.html

I just reviewed the documentation for preprepare -- I can see a use
case for that, but I really don't think it has a huge overlap with
my point. The parsing and planning mentioned in my point 3 would
apply to any query -- ad hoc, generated by an ORM, etc. The
preprepare project seems to be a way to create "persistent prepared
statements" which are automatically materialized upon connection.

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dimitri Fontaine 2009-12-28 22:58:36 Re: Admission Control Policy
Previous Message Dimitri Fontaine 2009-12-28 22:55:42 Re: Admission Control Policy