| From: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | "Bruce Momjian" <bruce(at)momjian(dot)us> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_index updates and SI invalidation |
| Date: | 2007-04-05 06:40:43 |
| Message-ID: | 2e78013d0704042340n572bb4bo6b1aaffebbed1451@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/3/07, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
>
> Where are we on this?
>
>
> ---------------------------------------------------------------------------
>
> Tom Lane wrote:
> >
> > [squint...] How can that fail during a reload if it worked the first
> > time? Needs a closer look at what's happening.
> >
>
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.
Thanks,
Pavan
--
EnterpriseDB http://www.enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| pg_index_SI_inval_v2.patch | application/octet-stream | 4.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2007-04-05 08:10:29 | Re: Auto Partitioning |
| Previous Message | Tom Lane | 2007-04-05 05:16:38 | Re: Modifying TOAST thresholds |