Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 765F79FA6B5 for ; Wed, 25 Oct 2006 20:23:44 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 47199-08 for ; Wed, 25 Oct 2006 20:23:42 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by postgresql.org (Postfix) with ESMTP id 7E72D9FA5D3 for ; Wed, 25 Oct 2006 20:23:41 -0300 (ADT) Received: by nf-out-0910.google.com with SMTP id g2so492397nfe for ; Wed, 25 Oct 2006 16:23:39 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=oR39BLBvqYeDxcSnFDFWOVhJlrmhlVODP1cMnGQJ+mkeIdP6bYNPUUVafrNf6B3nCp7VTJaG0Ao/V77c9urmwRECvVVIti2HCs289v2PC2+TBukmNIutYkAnEFEY8rTftvE/vUWeMbYvpfmYJHERPHp/mi31zsxDRiwZ8AWwObA= Received: by 10.49.93.13 with SMTP id v13mr4293110nfl; Wed, 25 Oct 2006 16:23:39 -0700 (PDT) Received: by 10.49.42.19 with HTTP; Wed, 25 Oct 2006 16:23:39 -0700 (PDT) Message-ID: <38242de90610251623x16e310b4oaf5192e9748268e6@mail.gmail.com> Date: Wed, 25 Oct 2006 17:23:39 -0600 From: "Joshua Marsh" To: pgsql-admin@postgresql.org Subject: Re: CLUSTER using more memory than expected In-Reply-To: <5929.1161816588@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_41296_18157759.1161818619388" References: <38242de90610250913s119e84c6rcf167edd74eadd60@mail.gmail.com> <5929.1161816588@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.458 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, HTML_40_50, HTML_MESSAGE, SPF_PASS X-Spam-Level: X-Archive-Number: 200610/169 X-Sequence-Number: 23472 ------=_Part_41296_18157759.1161818619388 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 10/25/06, Tom Lane 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. ------=_Part_41296_18157759.1161818619388 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

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.

------=_Part_41296_18157759.1161818619388--