The usefulness of this seems pretty dubious. You aren't going to have a
bunch of random bits of code sharing a connection; it's going to be a
single application that probably knows perfectly well exactly which
queries it needs prepared. So I don't think the stats will pay for
themselves.
Not true
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
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
