Search Postgresql Archives

Re: Prepared Statements

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am Sonntag 13 Januar 2008 00:46:50 schrieb Tom Lane:
> Kris Jurka <books@xxxxxxxxxx> writes:
> > On Thu, 10 Jan 2008, mljv@xxxxxxxxxxxx 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


---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your
       message can get through to the mailing list cleanly

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux