| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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.
--
Pip-pip
Sailesh
http://www.cs.berkeley.edu/~sailesh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sumaira Ali - | 2003-04-28 05:25:44 | LockData (Lock.h) |
| Previous Message | Tom Lane | 2003-04-28 04:57:10 | Re: Prepared queries and ANALYZE |