Re: Rule recompilation
От | Tom Lane |
---|---|
Тема | Re: Rule recompilation |
Дата | |
Msg-id | 11793.994966388@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Rule recompilation (Jan Wieck <JanWieck@Yahoo.com>) |
Ответы |
Re: Rule recompilation
|
Список | pgsql-hackers |
Jan Wieck <JanWieck@yahoo.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
В списке pgsql-hackers по дате отправления: