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 14703.1141832709@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  (Simon Riggs <simon@2ndquadrant.com>)
Re: problem with large maintenance_work_mem settings and  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
List pgsql-hackers
Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes:
> 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(!)

Cool.  Does it seem to be I/O bound now?  Would you be willing to do it
over with oprofile turned on?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Stefan Kaltenbrunner
Date:
Subject: Re: problem with large maintenance_work_mem settings and
Next
From: David Fetter
Date:
Subject: Add switches for DELIMITER and NULL in pg_dump COPY