Message-ID: <4D4069EF.6040603@agliodbs.com>
Date: Wed, 26 Jan 2011 10:37:35 -0800
From: Josh Berkus <josh@agliodbs.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US;
	rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2
MIME-Version: 1.0
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
References: <4D3F2D10.1020905@agliodbs.com> <21735.1295990515@sss.pgh.pa.us>
	<4D3F86D9.9080200@agliodbs.com> <14452.1296010153@sss.pgh.pa.us>
In-Reply-To: <14452.1296010153@sss.pgh.pa.us>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


> Your logic has nothing to do with what is actually happening.  Could we
> have a little bit more patience to see what happens next?

So, after 15 hours:

LOG:  finished writing run 20 to tape 19: CPU 588.86s/4484.35u sec
elapsed 5160.97 sec
STATEMENT:  create index "write_log_accounttime_idx" on write_log
(account_id, event_time);
LOG:  finished writing run 21 to tape 20: CPU 620.46s/4712.51u sec
elapsed 5435.63 sec
STATEMENT:  create index "write_log_accounttime_idx" on write_log
(account_id, event_time);
LOG:  finished writing run 22 to tape 21: CPU 654.01s/4953.74u sec
elapsed 5726.87 sec
STATEMENT:  create index "write_log_accounttime_idx" on write_log
(account_id, event_time);
LOG:  finished writing run 23 to tape 22: CPU 688.84s/5204.24u sec
elapsed 6029.41 sec
STATEMENT:  create index "write_log_accounttime_idx" on write_log
(account_id, event_time);
LOG:  finished writing run 24 to tape 23: CPU 721.71s/5442.40u sec
elapsed 6316.64 sec
STATEMENT:  create index "write_log_accounttime_idx" on write_log
(account_id, event_time);
LOG:  finished writing run 25 to tape 24: CPU 757.74s/5708.86u sec
elapsed 6636.64 sec
STATEMENT:  create index "write_log_accounttime_idx" on write_log
(account_id, event_time);
LOG:  finished writing run 26 to tape 25: CPU 790.87s/5946.83u sec
elapsed 6924.41 sec
STATEMENT:  create index "write_log_accounttime_idx" on write_log
(account_id, event_time);
LOG:  finished writing run 27 to tape 26: CPU 823.64s/6186.06u sec
elapsed 7212.11 sec
STATEMENT:  create index "write_log_accounttime_idx" on write_log
(account_id, event_time);

... I'll point out that the elapsed times which trace_sort is giving me
are clearly not clock times; I started this index run at 7pm PST
yesterday and it's been 15 hours, not 2 as the elapsed time would suggest.

-- 
                                  -- Josh Berkus
                                     PostgreSQL Experts Inc.
                                     http://www.pgexperts.com