From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
Cc: | "Bruce Momjian" <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_index updates and SI invalidation |
Date: | 2007-05-02 21:13:08 |
Message-ID: | 21320.1178140388@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> writes:
> Please see the attached updated patch, based on Tom's comments.
> Attempt to reload index information for system indexes such as
> pg_class_oid_index can cause infinite recursion. But I realized that
> we don't need to reload system index information because we
> neither allow CREATE INDEX or CIC on system relations. Only
> REINDEX is allowed which does not need any reload. So we skip
> index information reload for system relations.
Applied with revisions --- mostly, trying to keep the comments in sync
with the code. I also added a forced relcache inval on the index's
parent table at the end of CREATE INDEX CONCURRENTLY; this is to flush
cached plans and allow the newly valid index to be considered in
replanning. (The relcache inval on the index won't do it, since by
definition the index is not mentioned in any such plan...)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2007-05-02 21:28:26 | Re: Sequential scans |
Previous Message | Jeff Davis | 2007-05-02 21:11:48 | Re: Sequential scans |