From: | Volkan YAZICI <volkan(dot)yazici(at)gmail(dot)com> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_get_prepared? |
Date: | 2005-07-15 07:17:03 |
Message-ID: | 7104a73705071500171babd4ff@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 7/15/05, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> wrote:
> > You're mentioning about PHP PostgreSQL API, right?
>
> No, I'm talking about a PostgreSQL backend function.
Sorry, when you give a name like pg_get_prepared() (which is used in
PHP PostgreSQL API functions), I thought it's for PHP too.
> The use case is when you want to prepare a query, but only if it's not
> already prepared on that connection.
As Neil Conway explained on IRC - this feature can be useful for
connection pools. E.g. avoid re-preparing a stmt. if a previous client
using the conn. already prepared it.
> Same way that the EXECUTE command checks.
If it'll be done from backend, then there's no problem. I wondered the
PHP side of it. Anyway, it wasn't a PHP function.
Regards.
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2005-07-15 08:10:34 | Re: [Bizgres-general] A Guide to Constraint Exclusion |
Previous Message | Neil Conway | 2005-07-15 07:12:39 | Re: pg_get_prepared? |