Hi,
thank you very much
the article you referenced is what I was looking for.
>
> Prepared statements are per connection, and the actions taken at the
> close of a connection to pgpool to ready the pool for connection from a
> different client will very likely deallocate any prepared statements.
> The developers are usually actively trying to minimise pollution of
> state from one connection to the next, but persistence of prepared
> statements might be a different kettle of fish...
>
> Read here for more information. In paricular note that PREPARE has it's
> greatest impact when used on complex SQL - i.e. probably not INSERT
> statements:
>
> http://www.postgresql.org/docs/8.3/interactive/sql-prepare.html
--
V S P
toreason@fastmail.fm
--
http://www.fastmail.fm - A no graphics, no pop-ups email service