From: | Adrian von Bidder <avbidder(at)fortytwo(dot)ch> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: vulnerability of COPY command |
Date: | 2010-05-31 05:18:17 |
Message-ID: | 201005310718.24530@fortytwo.ch |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Heyho!
On Monday 31 May 2010 04.18:04 Dennis Gearon wrote:
> One thing, can prepared statements be done, including the 'execute',
> inside of a transaction, and what are the side effects?
Semantically, the statement is exactly like a "not prepared" statement: it
happens at execute time, the rest (prepare, variable binding) happens
independently of the transaction as far as I know.
Performance: there may be slight differencies since prepared statements will
cache the query plan. Unless you have relatively complex queries where the
execution plan depends heavily on the actual values to be bound to the
prepared statement this shouldn't matter much, though.
(Somebody please correct me if I'm wrong, I'm not a pg pro :-)
cheers
-- vbi
--
Today is Sweetmorn, the 5th day of Confusion in the YOLD 3176
Celebrate Syaday
From | Date | Subject | |
---|---|---|---|
Next Message | Devrim GÜNDÜZ | 2010-05-31 06:04:06 | Re: Fedora 13 and yum.pgsqlrpms.org |
Previous Message | Dennis Gearon | 2010-05-31 02:18:04 | Re: vulnerability of COPY command |