Skip site navigation (1) Skip section navigation (2)

Re: Prepared queries and ANALYZE

From: Sailesh Krishnamurthy <sailesh(at)cs(dot)berkeley(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: Prepared queries and ANALYZE
Date: 2003-04-28 05:01:02
Message-ID: bxyllxvmd0x.fsf@datafix.CS.Berkeley.EDU (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
>>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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 nice to 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.


In response to

pgsql-hackers by date

Next:From: Sumaira Ali -Date: 2003-04-28 05:25:44
Subject: LockData (Lock.h)
Previous:From: Tom LaneDate: 2003-04-28 04:57:10
Subject: Re: Prepared queries and ANALYZE

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group