Re: proposal for smaller indexes on index-ordered tables

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Jeffrey Baker" <jwbaker(at)gmail(dot)com>,"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal for smaller indexes on index-ordered tables
Date: 2008-06-24 22:01:15
Message-ID: 4861283D.EE98.0025.0@wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>> On Tue, Jun 24, 2008 at 4:54 PM, in message
<7020(dot)1214344479(at)sss(dot)pgh(dot)pa(dot)us>,
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Jeffrey Baker" <jwbaker(at)gmail(dot)com> writes:
>> Creating the table in this case takes half an
>> hour and then indexing it requires almost an hour.
>
> These numbers seem to me to be pretty strong evidence that
> maintenance_work_mem = 1GB is a mistake. Try it at 100MB and then
some
> intermediate values.
>
> Now, *why* it is a mistake is interesting to speculate about, but
> let's confirm the theory first.

Could this be related to hint bit rewrites during indexing?

Would a vacuum between creation and indexing be a good way to tell?

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-06-24 22:08:24 Re: proposal for smaller indexes on index-ordered tables
Previous Message Tom Lane 2008-06-24 21:54:39 Re: proposal for smaller indexes on index-ordered tables