Re: Improving backend launch time by preloading relcache - Mailing list pgsql-hackers

From Hiroshi Inoue
Subject Re: Improving backend launch time by preloading relcache
Date
Msg-id 3C5734BC.E1B875D9@tpf.co.jp
Whole thread Raw
In response to Improving backend launch time by preloading relcache  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Improving backend launch time by preloading relcache  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> 
> Hiroshi Inoue <Inoue@tpf.co.jp> writes:
> > Probably we don't have to keep the relhasindex info in the
> > db any longer and we had better keep some info about REINDEX
> > in memory local to the backend.
> 
> I never did much care for the "change relhasindex" hack.  Why isn't
> IsIgnoringSystemIndexes a sufficient solution?  I don't really care
> if REINDEX is a little bit slower than it might be, so just turning
> off use of *all* system indexes seems like an adequate answer.

It may be a reasonable solution.
I thought of another idea while reading the thread [HACKERS]
sequence indexes. Currently REINDEX recreates indexes from
the heap relations because the indexes may be corrupted.
However we can recreate indexes from existent ones if
they are sane. It would be a lot faster than the current
way for large tables. 

Comments ?

regards,
Hiroshi Inoue


pgsql-hackers by date:

Previous
From: Bill Studenmund
Date:
Subject: Re: RFD: schemas and different kinds of Postgres objects
Next
From: Hiroshi Inoue
Date:
Subject: Re: RFD: schemas and different kinds of Postgres objects