Re: Prepared statement already exists - Mailing list pgsql-general

From WireSpot
Subject Re: Prepared statement already exists
Date
Msg-id b2d4b0380811200356gdd5553fr5cb6e0555ea2d86b@mail.gmail.com
Whole thread Raw
In response to Prepared statement already exists  (WireSpot <wirespot@gmail.com>)
Responses Re: Prepared statement already exists  (Tomasz Ostrowski <tometzky@batory.org.pl>)
List pgsql-general
On Thu, Nov 20, 2008 at 10:56, Albe Laurenz <laurenz.albe@wien.gv.at> wrote:
> Do you still need the old prepared statement?
>
> If not, you can simple DEALLOCATE it and then try the PREPARE again.

Yes, I'd like to keep the old statements, that's part of the perks --
if a query will be repeated it will (possibly) benefit from the
statement being already prepared.

pgsql-general by date:

Previous
From: WireSpot
Date:
Subject: join with redundant results VS simpler join plus multiple selects
Next
From: Ivan Sergio Borgonovo
Date:
Subject: Re: transaction_read_only effects on performance, actual meaning (was: How to reduce impact of a query)