| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jan Wieck <JanWieck(at)yahoo(dot)com> |
| Cc: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>, PostgreSQL HACKERS <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Rule recompilation |
| Date: | 2001-07-12 19:33:08 |
| Message-ID: | 11793.994966388@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jan Wieck <JanWieck(at)yahoo(dot)com> writes:
> Stop!
> We're talking about two different things here.
You're right: fixing obsoleted querytrees stored in pg_rewrite and
similar catalogs is not the same thing as invalidating cached
query plans in plpgsql, SPI, etc.
However, we could turn them into the same problem if we rearrange the
catalogs to store only source text. Then there's no need to update any
permanent state, only a need to cause invalidation of derived state
inside various backends.
Each piece of derived state could (and should IMHO) be tagged with a
list of all the objects it depends on; then an invalidation message for
any of those objects would cause that piece of state to be thrown away
and rebuilt at next use. Just like the catalog caches ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-07-12 19:39:28 | Re: Rule recompilation |
| Previous Message | Bruce Momjian | 2001-07-12 19:29:09 | Re: [PATCH] Patch to make pg_hba.conf handle virtualhost access control and samehost keyword |