Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 1B77C9FB33D for ; Thu, 31 May 2007 12:44:41 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 69548-02 for ; Thu, 31 May 2007 12:44:28 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id DB8969FB4FC for ; Thu, 31 May 2007 12:44:33 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l4VFiUcq000119; Thu, 31 May 2007 11:44:30 -0400 (EDT) To: "Chris Hoover" cc: "pgsql-admin@postgresql.org" Subject: Re: Fwd: Out of Memory on Reindex In-reply-to: <1d219a6f0705310807r48bb141cy8ef5c77f49ac6196@mail.gmail.com> References: <1d219a6f0705290836h67b9509egc62498c78cf39829@mail.gmail.com> <1d219a6f0705301024p61aec66cv8b87adebfd4244a9@mail.gmail.com> <21900.1180562115@sss.pgh.pa.us> <1d219a6f0705310707i73292913rdccd98f591529776@mail.gmail.com> <29387.1180622575@sss.pgh.pa.us> <1d219a6f0705310807r48bb141cy8ef5c77f49ac6196@mail.gmail.com> Comments: In-reply-to "Chris Hoover" message dated "Thu, 31 May 2007 11:07:32 -0400" Date: Thu, 31 May 2007 11:44:30 -0400 Message-ID: <117.1180626270@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/335 X-Sequence-Number: 25655 "Chris Hoover" writes: > This is on a 32bit dual HT Xeon system using the official rpms. Um. I suspect you can't usefully set maintenance_work_mem as high as 1Gb in a 32-bit environment. Last I heard, the max address space available to userland in 32-bit Linux is 3Gb (the kernel takes the other Gb). Out of that you've got to subtract Postgres' shared memory, the program code itself, and whatever other random internal overhead a backend has got. I don't think you mentioned what shared memory settings you were using, but if you've been equally expansive on shared_buffers and so on it could easily be approaching 2Gb in shared memory. Try knocking maintenance_work_mem back to 512M or 256M and see if things get better. regards, tom lane