Re: using a lot of maintenance_work_mem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Frederik Ramm <frederik(at)remote(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: using a lot of maintenance_work_mem
Date: 2011-02-18 19:41:26
Message-ID: 13639.1298058086@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Frederik Ramm <frederik(at)remote(dot)org> writes:
> The single query where pg9.0 beat pg8.3 by a country mile was a CREATE
> INDEX statement on a BIGINT column to a table with about 500 million
> records - this cost 2679 seconds on normal 8.3, 2443 seconds on
> large-memory 8.3, and aroung 1650 seconds on 9.0, large memory or not.

FWIW, that's probably due to bigint having become pass-by-value on
64-bit platforms.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2011-02-18 19:41:27 Re: WIP - Add ability to constrain backend temporary file space
Previous Message Tom Lane 2011-02-18 19:39:17 Re: Assertion failure on UNLOGGED VIEW and SEQUENCE