pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: andrew@pillette.com
Cc: pgsql-performance@postgresql.org
Subject: Re: What *_mem to increase when running CLUSTER
Date: Thu, 25 Aug 2005 16:19:50 -0400
Message-ID: <14786.1125001190@sss.pgh.pa.us> (raw)
In-Reply-To: <430E1AF6.9030803@pillette.com>
References: <6EE64EF3AB31D5448D0007DD34EEB3417DD1D2@Herge.rcsinc.local>
	<430E1AF6.9030803@pillette.com>

Andrew Lazarus <andrew@pillette.com> writes:
> Should I temporarily increase sort_mem, vacuum_mem, neither, or both 
> when doing a CLUSTER on a large (100 million row) table

The only part of that job that can use lots of memory is the index
rebuilds.  In recent PG versions maintenance_work_mem is the thing
to increase for an index build; previously sort_mem controlled it.
I forget when the changeover was; maybe 8.0.

			regards, tom lane



view thread (3+ messages)

Message-ID: <14786.1125001190@sss.pgh.pa.us>
Permalink:  ../14786.1125001190@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/14786.1125001190@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, andrew@pillette.com
  Subject: Re: What *_mem to increase when running CLUSTER
  In-Reply-To: <14786.1125001190@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox