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-30 07:54:05
Message-ID: 3C57A69D.4851002E@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
>
> Hmm ... you are thinking about the case where REINDEX is being used
> not to recover from corruption, but just to shrink indexes that have
> accumulated too much free space.

Yes.

> Okay, that's a reasonable case to
> try to optimize, though I'd like to think the problem will go away
> in a release or two when we implement VACUUM-time index shrinking.
>
> However, I'm not sure about the "lot faster" part. The only win
> I can see is that when rebuilding a btree index, you could skip
> the sort step by reading the old index in index order.

Don't we have to scan the (possibly larger) heap table ?

regards,
Hiroshi Inoue

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas SB SD 2002-01-30 08:43:24 Re: Per-database and per-user GUC settings
Previous Message Tom Lane 2002-01-30 06:33:03 Re: Improving backend launch time by preloading relcache