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-28 02:48:05
Message-ID: 2e78013d0703271948m6630197dge73acfaf6c4206a2@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

And what's the point of
> the extra tuple copy step, instead of assigning the values into the
> cache entry immediately?

Oops, sorry. Thats a copy-paste error. We certainly don't need
to copy the tuple.

Thanks,
Pavan

--

EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2007-03-28 02:55:41 Re: Patch queue concern
Previous Message Andrew Dunstan 2007-03-28 02:15:13 Re: Warning on contrib/tsearch2