Re: vulnerability of COPY command - Mailing list pgsql-general

From Adrian von Bidder
Subject Re: vulnerability of COPY command
Date
Msg-id 201005310718.24530@fortytwo.ch
Whole thread Raw
In response to Re: vulnerability of COPY command  (Dennis Gearon <gearond@sbcglobal.net>)
List 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

Attachment

pgsql-general by date:

Previous
From: Dennis Gearon
Date:
Subject: Re: vulnerability of COPY command
Next
From: Devrim GÜNDÜZ
Date:
Subject: Re: Fedora 13 and yum.pgsqlrpms.org