Re: Prepared queries and ANALYZE - Mailing list pgsql-hackers

From Gavin Sherry
Subject Re: Prepared queries and ANALYZE
Date
Msg-id Pine.LNX.4.21.0304281532240.21086-100000@linuxworld.com.au
Whole thread Raw
In response to Re: Prepared queries and ANALYZE  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, 28 Apr 2003, Tom Lane wrote:

> Gavin Sherry <swm@linuxworld.com.au> writes:
> > Looking through the query preparing and stats analyze code, I noticed that
> > prepared queries using an analyzed table are not replanned. I imagine that
> > some users of prepared queries would not want the above behaviour, plan
> > stability etc, but surely others would.
> > I didn't notice any discusion of this in the list archives. Any technical
> > reasons why this shouldn't happen?
> 
> Well, there are implementation reasons why it doesn't happen: there's no
> infrastructure for determining which tables a prepared query depends on
> nor for re-planning it if we did notice they'd changed.

Yes. Speaking to Bruce on IRC I was reminded that prepared queries exist
on a single backend which makes such this problem less pertinent than a
general solution, which you mentioned.

Gavin



pgsql-hackers by date:

Previous
From: "Sumaira Ali -"
Date:
Subject: LockData (Lock.h)
Next
From: "Zeugswetter Andreas SB SD"
Date:
Subject: Re: STABLE functions