Re: Improving backend launch time by preloading relcache

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Improving backend launch time by preloading relcache
Date: 2002-01-29 23:48:12
Message-ID: 3C5734BC.E1B875D9@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
>
> Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hiroshi Inoue 2002-01-30 00:20:46 Re: RFD: schemas and different kinds of Postgres objects
Previous Message Lamar Owen 2002-01-29 22:02:16 Re: 7.2 RPMs (Re: [HACKERS] PostgreSQL v7.2rc2 Released)