From: Joshua Marsh <icub3d@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: CLUSTER using more memory than expected
Date: Wed, 25 Oct 2006 17:23:39 -0600
Message-ID: <38242de90610251623x16e310b4oaf5192e9748268e6@mail.gmail.com> (raw)
In-Reply-To: <5929.1161816588@sss.pgh.pa.us>
References: <38242de90610250913s119e84c6rcf167edd74eadd60@mail.gmail.com>
<5929.1161816588@sss.pgh.pa.us>
On 10/25/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
>
> CLUSTER will eat maintenance_work_mem during index rebuilds --- more or
> less. You shouldn't expect these numbers to be dead on, particularly
> not in older releases. It looks like your 2Gb spec has turned into
> 3.6Gb actually eaten, which is a bit sloppier accounting than I'd like
> but not overly surprising. (FWIW, I think CVS HEAD is better than 8.0
> at measuring sort workspace.)
>
> regards, tom lane
>
Thanks for the clarification. It doesn't sound like it's going to jump to
8Gb and hog most of the RAM.
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: icub3d@gmail.com
Subject: Re: CLUSTER using more memory than expected
In-Reply-To: <38242de90610251623x16e310b4oaf5192e9748268e6@mail.gmail.com>
References: <38242de90610250913s119e84c6rcf167edd74eadd60@mail.gmail.com> <5929.1161816588@sss.pgh.pa.us> <38242de90610251623x16e310b4oaf5192e9748268e6@mail.gmail.com>
* 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