Re: problem with large maintenance_work_mem settings and

Tom Lane wrote:
> Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)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.

playing with CVS tip right now, it is a bit faster for both the initial
bulkloading (about 5%) and for the CREATE INDEX itself (11h30min vs
11h54min) though not a dramatic improvement.

Stefan