Received: from localhost (unknown [200.46.204.184])
	by postgresql.org (Postfix) with ESMTP id 53A199FB61D
	for <pgsql-performance-postgresql.org@postgresql.org>;
	Tue, 16 Oct 2007 11:33:22 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024)
	with ESMTP id 38894-09 for
	<pgsql-performance-postgresql.org@postgresql.org>;
	Tue, 16 Oct 2007 11:33:01 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.5
Received: from mir3-fs.mir3.com (mail.mir3.com [72.11.241.14])
	by postgresql.org (Postfix) with ESMTP id DF6279FB611
	for <pgsql-performance@postgresql.org>;
	Tue, 16 Oct 2007 11:33:18 -0300 (ADT)
Received: MIR3-FS.mir3.com 172.16.1.11 from 172.16.2.68 172.16.2.68 via HTTP
	with MS-WebStorage 6.0.6249
Received: from archimedes by MIR3-FS.mir3.com; 16 Oct 2007 07:33:15 -0700
Subject: Re: Autovacuum running out of memory
From: Mark Lewis <mark.lewis@mir3.com>
To: Jason Lustig <lustig@brandeis.edu>
Cc: Richard Huxton <dev@archonet.com>, pgsql-performance@postgresql.org
In-Reply-To: <A727D61D-09FC-4174-B120-18D5C3D5D475@brandeis.edu>
References: <374EB3D1-EE74-4B8C-9EEC-104ADD097568@brandeis.edu>
	<4714A458.5060408@archonet.com>
	<E8328FA1-800E-4684-93D2-A1002BB72396@brandeis.edu>
	<4714AD30.6000103@archonet.com>
	<57031F92-40D5-4832-8B76-FB73E510C735@brandeis.edu>
	<4714C426.3080207@archonet.com>
	<A727D61D-09FC-4174-B120-18D5C3D5D475@brandeis.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Organization: MIR3, Inc.
Date: Tue, 16 Oct 2007 07:33:15 -0700
Message-Id: <1192545195.6447.54.camel@archimedes>
Mime-Version: 1.0
X-Mailer: Evolution 2.8.1 
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200710/180
X-Sequence-Number: 27202

On Tue, 2007-10-16 at 10:14 -0400, Jason Lustig wrote:
> I ran "ulimit -a" for the postgres user, and here's what I got:
...
> max memory size         (kbytes, -m) 200000
> open files                      (-n) 100
> max user processes              (-u) 100
> virtual memory          (kbytes, -v) 200000
...

These settings are all quite low for a dedicated database server, they
would be more appropriate for a small development instance of PG sharing
a machine with several other processes.

Others have commented on the memory settings, but depending on the
maximum number of connections you expect to have open at any time you
may want to consider increasing the max user processes and open files
settings as well.

-- Mark Lewis