Re: Prepared Statements - Mailing list pgsql-general

From Janning Vygen
Subject Re: Prepared Statements
Date
Msg-id 200801131213.55570.vygen@planwerk6.de
Whole thread Raw
In response to Re: Prepared Statements  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Am Sonntag 13 Januar 2008 00:46:50 schrieb Tom Lane:
> Kris Jurka <books@ejurka.com> writes:
> > On Thu, 10 Jan 2008, mljv@planwerk6.de wrote:
> >> What do you mean with "longer lifespan"? Doesn't the JDBC driver uses
> >> the PREPARE Sql Statement and therefore the prepared Statement has the
> >> same lifespan as the connection? If so, as connections are pooled and
> >> never closed, the prepared Statement will last forever. What if the
> >> table analyzes changes and a better execution plan could be found?
> >
> > Data and stats changes do not trigger a replan.
>
> Note that this is no longer true as of 8.3: a stats update from ANALYZE
> (either manual or autovacuum) will trigger invalidation of cached plans.

great, i have too look out for 8.3, but i am quite happy with 8.1 because of
automatic security updates coming with debian out of the box. I have to look
for another way to replan. Maybe i just have to close and reopen my
connections from time to time.

kind regards
Janning


pgsql-general by date:

Previous
From: hiddenhippo
Date:
Subject: backup and restore
Next
From: "Andrus"
Date:
Subject: COUNT() with ORDER BY