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

From Sailesh Krishnamurthy
Subject Re: Prepared queries and ANALYZE
Date
Msg-id bxyllxvmd0x.fsf@datafix.CS.Berkeley.EDU
Whole thread Raw
In response to Re: Prepared queries and ANALYZE  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
>>>>> "Tom" == Tom Lane <tgl@sss.pgh.pa.us> writes:
   Tom> But really this is a special case of the problem of "schema   Tom> changed underneath a plan", and yes it'd be
niceto notice   Tom> that and invalidate the plan.
 

In general, pgsql doesn't cache access plans, correct ? 

If there was a cache of access plans, repeated queries (not just
prepared by the same client) could use the same plan avoiding
recompilation. The cache will also be a single place in shared memory
where invalidation can take place.

Just my 2c.

-- 
Pip-pip
Sailesh
http://www.cs.berkeley.edu/~sailesh



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Prepared queries and ANALYZE
Next
From: "Sumaira Ali -"
Date:
Subject: LockData (Lock.h)