From: | Janning Vygen <vygen(at)planwerk6(dot)de> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Prepared Statements |
Date: | 2008-01-13 11:13:55 |
Message-ID: | 200801131213.55570.vygen@planwerk6.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Am Sonntag 13 Januar 2008 00:46:50 schrieb Tom Lane:
> Kris Jurka <books(at)ejurka(dot)com> writes:
> > On Thu, 10 Jan 2008, mljv(at)planwerk6(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Meskes | 2008-01-13 11:54:36 | Re: ECPG problem with 8.3 |
Previous Message | alphax | 2008-01-13 11:11:08 | Re: How to safely compare transaction id? |