Re: problem with large maintenance_work_mem settings and - Mailing list pgsql-hackers

From Tom Lane
Subject Re: problem with large maintenance_work_mem settings and
Date
Msg-id 25568.1141501156@sss.pgh.pa.us
Whole thread Raw
In response to Re: problem with large maintenance_work_mem settings and  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
Responses Re: problem with large maintenance_work_mem settings and  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
List pgsql-hackers
Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes:
>>> forgot to mention that this is 8.1.3 compiled from source.
>> 
>> See the discussion starting here:
>> http://archives.postgresql.org/pgsql-hackers/2006-02/msg00590.php

> I was following this thread - and it was partly a reason why I'm playing
> with that(the CREATE INDEX on that table finished after about 12 hours
> with a bit less 2GB for maintenance_work_mem(for comparision it took me
> only about 2,5hours to create this table) .

It would be interesting to try the same test with CVS tip to see if the
sorting improvements Simon and I made over the past few weeks help much.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Stefan Kaltenbrunner
Date:
Subject: EXPLAIN and HashAggregate
Next
From: Tom Lane
Date:
Subject: Re: EXPLAIN and HashAggregate