Re: Global Named Prepared Statements

On Tue, May 15, 2012 at 05:38:27AM +0530, Samba wrote:
> Hi,
>
> Does postgresql support Global Prepared Statements, which are prepared only
> once per server and not per every connection?

As pointed out, no.

> Problem with per-connection prepared statements is that the onus of
> preparing those statements for each connection lies with the client which
> makes those connections. Ideally, the performance of an application must be
> decided by the Server that hosts and not by the client that uses the
> service.

How is this different from using CREATE FUNCTION to create a function
which has the desired effect? This is a well understood and commonly
used paradigm. When using a connection pooler any query plan caching
will happen automatically.

Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> He who writes carelessly confesses thereby at the very outset that he does
> not attach much importance to his own thoughts.
-- Arthur Schopenhauer