| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | David Brown <dave(at)spoonguard(dot)org> |
| Cc: | PostgreSQL Global Development Group <pgsql-patches(at)postgresql(dot)org>, Charlie Peck <charliep(at)cs(dot)earlham(dot)edu> |
| Subject: | Re: Allow pooled connections to list all prepared queries |
| Date: | 2004-12-26 00:05:07 |
| Message-ID: | Pine.BSO.4.56.0412251859460.17812@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On Wed, 22 Dec 2004, David Brown wrote:
> This would allow an application inheriting a pooled connection to know
> the queries prepared in the current session.
>
I don't see this as all that helpful for a client interface that does the
preparation itself. Possibly it could be used for libpq, but you
mentioned DBI which should already know what it has or has not prepared.
The idea of adding a network round trip to detect a prepared statement
seems like a performance loss, not a gain. If this is just to avoid
repreparing the same statement then perhaps something like PREPARE OR
REPLACE would be more useful.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Brown | 2004-12-26 02:08:23 | Re: Allow pooled connections to list all prepared queries |
| Previous Message | David Brown | 2004-12-24 20:34:29 | Re: Allow pooled connections to list all prepared queries |