| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | hf1122x(at)protecting(dot)net, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: invalidating cached plans |
| Date: | 2005-03-15 01:24:40 |
| Message-ID: | 42363958.8040001@samurai.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian wrote:
> One idea would be to record if the function uses non-temp tables, temp
> tables, or both, and invalidate based on the type of table being
> invalidated, rather than the table name itself. I can imagine this
> hurting temp table caching, but at least functions using regular tables
> would not be affected, and functions using temp tables would work
> reliably.
It seems to me it's not _that_ difficult to invalidate plans at a more
granular level (based on the individual database objects they depend
upon). Inlined functions need to be handled, but that is doable -- it
just needs some work. The efficiency win of not needlessly throwing away
cached plans is worth investing some effort, I think.
-Neil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Qingqing Zhou | 2005-03-15 01:25:33 | Re: invalidating cached plans |
| Previous Message | Bruce Momjian | 2005-03-15 01:06:46 | Re: invalidating cached plans |