From: Josh Berkus <josh@agliodbs.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@postgresql.org
Subject: Re: Multicolun index creation never completes on 9.0.1/solaris
Date: Tue, 25 Jan 2011 18:57:03 -0800
Message-ID: <4D3F8D7F.6020806@agliodbs.com> (raw)
In-Reply-To: <14452.1296010153@sss.pgh.pa.us>
References: <4D3F2D10.1020905@agliodbs.com>
<21735.1295990515@sss.pgh.pa.us>
<4D3F86D9.9080200@agliodbs.com>
<14452.1296010153@sss.pgh.pa.us>
>> If it's going to take 3 minutes each to write each of 3745 tapes, that
>> means completing in around 9 days.
>
> Your logic has nothing to do with what is actually happening. Could we
> have a little bit more patience to see what happens next?
OK, I'll let it run overnight and give you the trace output.
> (Memo to -hackers: what we lack in this trace is any indication of how
> long the runs are. Maybe should add that. Knuth claims the initial
> runs should amount to about 2X maintenance_work_mem on average, but
> maybe there's something unusual about the data distribution here.)
Well, for the straight test on event_time, the rows in the table should
have been more-or-less physically already in order. This table is
most-insert, and event_time mostly corresponds to current server time.
For the composite index, rows would be more randomly distributed.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: josh@agliodbs.com, tgl@sss.pgh.pa.us
Subject: Re: Multicolun index creation never completes on 9.0.1/solaris
In-Reply-To: <4D3F8D7F.6020806@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox