On Wed, 2006-03-08 at 10:45 -0500, Tom Lane wrote:
> Stefan Kaltenbrunner <[EMAIL PROTECTED]> 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?
Very.
Any chance of trying it with different maintenance_work_mem settings?
Did you try this with trace_sort=on? If so could we get the logs for
that?
[Results welcome from other hackers...particularly with regard to
queries with sort steps in rather than CREATE INDEX.]
Best Regards, Simon Riggs
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
