| From: | Mario Weilguni <mweilguni(at)sime(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
| Subject: | Re: pg_get_prepared? |
| Date: | 2005-07-16 11:22:30 |
| Message-ID: | 200507161122.31207.mweilguni@sime.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Am Freitag, 15. Juli 2005 14:19 schrieb Greg Sabino Mullane:
> > The use case is when you want to prepare a query, but only if it's not
> > already prepared on that connection.
>
> This has been covered before, but to reiterate: why would you need this?
> Any application worth its salt should be tracking which statements it
> has already prepared (after all, they cannot span connections). Seems
> a waste of resources to make a separate call to the database for
> information you should already know.
Does not apply to mod_php/apache, you simply do not know if a connection made
my pg_pconnect is a new connection or a reused one. That has nothing to do
with the application itself.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-07-16 11:48:42 | Re: Checkpoint cost, looks like it is WAL/CRC |
| Previous Message | Marko Kreen | 2005-07-16 10:07:41 | Re: [HACKERS] 4 pgcrypto regressions failures - 1 unsolved |