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:03:48 -0500
Message-ID: <14694.1296011028@sss.pgh.pa.us> (raw)
In-Reply-To: <4D3F8A9E.8070608@agliodbs.com>
References: <4D3F2D10.1020905@agliodbs.com>
<21735.1295990515@sss.pgh.pa.us>
<4D3F8A9E.8070608@agliodbs.com>
Josh Berkus <josh@agliodbs.com> writes:
> OK, either tape sort is broken or trace_sort is. The larger my
> maint_work_mem, the MORE tapes it wants to use:
Yeah, that's right. More tapes = better, or at least that was the
conclusion we came to some years ago. It doesn't necessarily use all
those tapes --- it's hoping it will find that the data sorts into fewer
runs than that, and it can go directly to the final merge without any
intermediate merge passes.
It's conceivable that there's an upper bound to the number of tapes we
should try to use, but you really haven't provided any data that would
either confirm or refute that idea.
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: <14694.1296011028@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