On 1/25/11 1:21 PM, Tom Lane wrote:
> Josh Berkus <j...@agliodbs.com> writes:
>> Note: I have this running now on a test box. If someone responds in the
>> next couple hours, I can run whatever diagnostics you want on it.
>> Otherwise I'll kill it off and start over with debug logging turned on.
>
> trace_sort would be interesting.
OK, either tape sort is broken or trace_sort is. The larger my
maint_work_mem, the MORE tapes it wants to use:
LOG: begin index sort: unique = f, workMem = 4194304, randomAccess = f
LOG: switching to external sort with 14980 tapes: CPU 33.33s/24.23u sec
elapsed 58.86 sec
LOG: begin index sort: unique = f, workMem = 131072, randomAccess = f
LOG: switching to external sort with 469 tapes: CPU 1.87s/1.48u sec
elapsed 3.47 sec
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
