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

From Stefan Kaltenbrunner
Subject Re: problem with large maintenance_work_mem settings and
Date
Msg-id 440EF9AF.6070407@kaltenbrunner.cc
Whole thread Raw
In response to Re: problem with large maintenance_work_mem settings and  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: problem with large maintenance_work_mem settings and
List pgsql-hackers
Tom Lane wrote:
> I wrote:
> 
>>Stefan Kaltenbrunner <stefan@kaltenbrunner.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


pgsql-hackers by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: [PATCHES] Inherited Constraints
Next
From: Tom Lane
Date:
Subject: Re: problem with large maintenance_work_mem settings and