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: Wed, 26 Jan 2011 15:13:02 -0500
Message-ID: <24466.1296072782@sss.pgh.pa.us> (raw)
In-Reply-To: <4D40795A.8000103@agliodbs.com>
References: <4D3F2D10.1020905@agliodbs.com>
<21735.1295990515@sss.pgh.pa.us>
<4D3F86D9.9080200@agliodbs.com>
<14452.1296010153@sss.pgh.pa.us>
<4D4069EF.6040603@agliodbs.com>
<23139.1296069017@sss.pgh.pa.us>
<4D40795A.8000103@agliodbs.com>
Josh Berkus <josh@agliodbs.com> writes:
> Oh! Actually, it only *did* 27 runs. So it actually completed building
> the index. I'd expected trace_sort to give me some kind of completion
> message; apologies for not checking all screen windows.
Huh, there should be an "external sort ended" message, as well as some
other ones once it finishes writing the initial runs.
> So, why didn't the index build complete (after more than 36 hours) when
> I ran it as part of pg_restore? I guess this goes back to being a
> pg_restore problem and not an index build problem.
First thing that comes to mind is to wonder what maintenance_work_mem
setting was in effect for the pg_restore run.
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: <24466.1296072782@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