Re: Prepared statement performance...

Neil Conway <neilc@samurai.com>

From: Neil Conway <neilc@samurai.com>
To: Dmitry Tkach <dmitry@openratings.com>
Cc: pgsql-general@postgresql.org, pgsql-jdbc@postgresql.org
Date: 2002-09-25T17:17:56Z
Lists: pgsql-general
Dmitry Tkach <dmitry@openratings.com> writes:
> - a general solution, that would involve extending postgres SQL gramma
> to include a 'prepare' statement

As someone else mentioned, this has been implemented for 7.3. I
implemented PREPARE/EXECUTE/DEALLOCATE on the backend side, Barry Lind
(I believe) added support for using backend prepared statements to the
JDBC driver.

> The second solution is not only ugly (because it requires the
> application code to be changed and to have a specialized stored
> procedure for every query), but also requires some additional hacks
> (to overcome the hard limit on the number of function arguments and
> the inability for functions to return tuples)

Note that in 7.3, functions can return sets of tuples.

Cheers,

Neil

-- 
Neil Conway <neilc@samurai.com> || PGP Key ID: DB3C29FC