From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-bugs@postgresql.org
Subject: Re: Multicolun index creation never completes on 9.0.1/solaris
Date: Tue, 25 Jan 2011 22:09:52 -0500
Message-ID: <14811.1296011392@sss.pgh.pa.us> (raw)
In-Reply-To: <4D3F8D7F.6020806@agliodbs.com>
References: <4D3F2D10.1020905@agliodbs.com>
<21735.1295990515@sss.pgh.pa.us>
<4D3F86D9.9080200@agliodbs.com>
<14452.1296010153@sss.pgh.pa.us>
<4D3F8D7F.6020806@agliodbs.com>
Josh Berkus <josh@agliodbs.com> writes:
> 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.
That would result in a very long initial run (probably all or most of
the data), which fits with your observation so far. But we don't know
what happens after that.
BTW, are you paying attention to vmstat or similar measure of the amount
of I/O and CPU work getting done? vmstat data ought to make it possible
to estimate the size of those runs, even though the trace_sort logic
isn't telling us.
regards, tom lane
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: tgl@sss.pgh.pa.us, josh@agliodbs.com
Subject: Re: Multicolun index creation never completes on 9.0.1/solaris
In-Reply-To: <14811.1296011392@sss.pgh.pa.us>
* 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