Postgres Pro
Downloads
Home   >   mailing lists

Re: pg_index updates and SI invalidation - Mailing list pgsql-hackers

From Pavan Deolasee
Subject Re: pg_index updates and SI invalidation
Date
Msg-id 2e78013d0703271948m6630197dge73acfaf6c4206a2@mail.gmail.com
Whole thread Raw
In response to Re: pg_index updates and SI invalidation  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_index updates and SI invalidation  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view


On 3/28/07, Tom Lane <tgl@sss.pgh.pa.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

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Warning on contrib/tsearch2
Next
From: Josh Berkus
Date:
Subject: Re: Patch queue concern