Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 3A03A64FC60 for ; Mon, 17 Nov 2008 04:56:00 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 84103-05 for ; Mon, 17 Nov 2008 04:55:56 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mail.postgresql.org (Postfix) with ESMTP id 9852064FC5C for ; Mon, 17 Nov 2008 04:55:56 -0400 (AST) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id 7D55B1B697F; Mon, 17 Nov 2008 03:55:55 -0500 (EST) Received: from web5.messagingengine.com ([10.202.2.214]) by compute2.internal (MEProxy); Mon, 17 Nov 2008 03:55:55 -0500 Received: by web5.messagingengine.com (Postfix, from userid 99) id 5FFA125A24; Mon, 17 Nov 2008 03:55:55 -0500 (EST) Message-Id: <1226912155.25672.1285154419@webmail.messagingengine.com> X-Sasl-Enc: dSlPKlhwWWldfTuXPmFJP6EQHUxzDQYRw52kXjFY6MIM 1226912155 From: "V S P" To: "Andrew McMillan" Cc: pgsql-php@postgresql.org Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="KOI8-R" MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface References: <1226803530.24888.1284994985@webmail.messagingengine.com> <492093A5.7040606@gmail.com> <20081117002630.d86160fd.knl@bitflop.com> <1226890873.32288.1285117971@webmail.messagingengine.com> (sfid-20081117_160220_914818_FB8966C0) <1226894747.5577.267.camel@happy.mcmillan.net.nz> <1226896018.14093.1285127497@webmail.messagingengine.com> (sfid-20081117_173237_571180_472D2DD1) <1226910402.5577.280.camel@happy.mcmillan.net.nz> Subject: Re: [Q] PDO use to bind arrays for insert In-Reply-To: <1226910402.5577.280.camel@happy.mcmillan.net.nz> Date: Mon, 17 Nov 2008 03:55:55 -0500 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200811/17 X-Sequence-Number: 3928 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