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
V S P
http://www.fastmail.fm - A no graphics, no pop-ups email service
In response to
pgsql-php by date
|Next:||From: V S P||Date: 2008-11-21 06:54:35|
|Subject: [Q] storing JSON, problem with 'escapes'|
|Previous:||From: Andrew McMillan||Date: 2008-11-17 08:26:42|
|Subject: Re: [Q] PDO use to bind arrays for insert|