Re: problem with large maintenance_work_mem settings and

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: problem with large maintenance_work_mem settings and
Date: 2006-03-08 15:35:11
Message-ID: 440EF9AF.6070407@kaltenbrunner.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> I wrote:
>
>>Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
>>
>>>samples % symbol name
>>>24915704 96.2170 ltsReleaseBlock
>
>
>>We probably need to tweak things so this doesn't get called during the
>>"final merge" pass. Looking at it now.
>
>
> I've committed a fix for this into CVS HEAD --- please try it out.

just tried that with CVS HEAD (includes the second fix too):

CREATE INDEX on a 1,8B row table (5 int columns - index created on the
first row about 300M distinct values):

before: 11h 51min
after: 3h 11min(!)

Stefan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-03-08 15:45:09 Re: problem with large maintenance_work_mem settings and
Previous Message Stephan Szabo 2006-03-08 15:35:01 Re: [PATCHES] Inherited Constraints