Re: pg_index updates and SI invalidation

From: "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_index updates and SI invalidation
Date: 2007-03-26 18:01:20
Message-ID: 2e78013d0703261101y513f16fbj78a11273f57d0571@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 3/26/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>
> Hmm ... actually, CREATE INDEX CONCURRENTLY gets this wrong already, no?
> I suspect that sessions existing at the time C.I.C is done will never
> see the new index as valid, unless something else happens to make them
> drop and rebuild their relcache entries for it.
>
>

Yes, C.I.C gets it wrong. I confirmed that new index is seen as invalid
for existing sessions. Is it something we should fix ?

Thanks,
Pavan

--

EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-03-26 18:07:40 Re: notification payloads
Previous Message Tom Lane 2007-03-26 17:55:37 Re: tsearch_core for inclusion