Skip site navigation (1) Skip section navigation (2)

Re: pg_index updates and SI invalidation

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_index updates and SI invalidation
Date: 2007-04-02 23:59:21
Message-ID: 200704022359.l32NxLx27510@momjian.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Where are we on this?

---------------------------------------------------------------------------

Tom Lane wrote:
> "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> writes:
> > On 3/28/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> It seems a bit brute-force.  Why didn't you use SearchSysCache(INDEXRELID)
> >> the same as RelationInitIndexAccessInfo does?
> 
> > I tried that initially, but it gets into infinite recursion during initdb.
> 
> [squint...]  How can that fail during a reload if it worked the first
> time?  Needs a closer look at what's happening.
> 
> 			regards, tom lane
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
> 
>                http://www.postgresql.org/docs/faq

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>          http://momjian.us
  EnterpriseDB                               http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

In response to

Responses

pgsql-hackers by date

Next:From: Gavin SherryDate: 2007-04-03 00:03:40
Subject: Re: Many unfinished patches
Previous:From: Bruce MomjianDate: 2007-04-02 23:31:33
Subject: Many unfinished patches

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group