Re: proposal for smaller indexes on index-ordered tables - Mailing list pgsql-hackers

From Tom Lane
Subject Re: proposal for smaller indexes on index-ordered tables
Date
Msg-id 7246.1214345304@sss.pgh.pa.us
Whole thread Raw
In response to Re: proposal for smaller indexes on index-ordered tables  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: proposal for smaller indexes on index-ordered tables  ("Jeffrey Baker" <jwbaker@gmail.com>)
List pgsql-hackers
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> Tom Lane <tgl@sss.pgh.pa.us> wrote: 
>> 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?

If so, changing maintenance_work_mem won't improve the situation.

What I personally suspect is that Jeff's index build is swapping like
crazy, or else there's just some problem in the sort code for such a
large sort arena.  But let's get some evidence about how the index build
time varies with maintenance_work_mem before jumping to conclusions.

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

Yeah, that might be a useful experiment to try too.  It wouldn't improve
the overall time AFAICS, but it would give us some idea how much of the
indexing time was really spent on hintbits.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: proposal for smaller indexes on index-ordered tables
Next
From: "Jeffrey Baker"
Date:
Subject: Re: proposal for smaller indexes on index-ordered tables