From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: vacuum timings |
Date: | 2000-01-22 05:17:36 |
Message-ID: | 200001220517.AAA03032@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Conclusions:
> > o drop/recreate index is slower than vacuum of indexes
>
> BTW, I did some profiling of CREATE INDEX this evening (quite
> unintentionally actually; I was interested in COPY IN, but the pg_dump
> script I used as driver happened to create some indexes too). I was
> startled to discover that 60% of the runtime of CREATE INDEX is spent in
> _bt_invokestrat (which is called from tuplesort.c's comparetup_index,
> and exists only to figure out which specific comparison routine to call).
> Of this, a whopping 4% was spent in the useful subroutine, int4gt. All
> the rest went into lookup and validation checks that by rights should be
> done once per index creation, not once per comparison.
Good job, Tom. Clearly a huge win.
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Micheal H. | 2000-01-22 06:54:34 | No suitable driver problem |
Previous Message | Tom Lane | 2000-01-22 04:50:13 | Re: vacuum timings |