X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id BD431329C6B for ; Sun, 12 Sep 2004 06:43:15 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 47073-05 for ; Sun, 12 Sep 2004 05:43:13 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 6260A329C67 for ; Sun, 12 Sep 2004 06:43:13 +0100 (BST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i8C5h9pr012800; Sun, 12 Sep 2004 01:43:09 -0400 (EDT) To: "C. Bensend" Cc: pgsql-admin@postgresql.org Subject: Re: Memory exhausted in AllocSetAlloc In-reply-to: <60549.63.227.74.41.1094956933.squirrel@63.227.74.41> References: <60549.63.227.74.41.1094956933.squirrel@63.227.74.41> Comments: In-reply-to "C. Bensend" message dated "Sat, 11 Sep 2004 21:41:51 -0500" Date: Sun, 12 Sep 2004 01:43:09 -0400 Message-ID: <12799.1094967789@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200409/108 X-Sequence-Number: 14811 "C. Bensend" writes: > I understand what happened, but not exactly why - this machine is > running with over 300M of RAM unused. Bumping this value down to 16M > works fine. But why does it hit a memory exhausted error at 64M? Maybe it's exceeding a ulimit setting? You might want to watch it with "top" and see what size the process actually gets to before failing. I'm not sure how accurate the vacuum_mem throttle is ... regards, tom lane