From: Mark Lewis <mark.lewis@mir3.com>
To: Jason Lustig <lustig@brandeis.edu>
Cc: Richard Huxton <dev@archonet.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Autovacuum running out of memory
Date: Tue, 16 Oct 2007 07:33:15 -0700
Message-ID: <1192545195.6447.54.camel@archimedes> (raw)
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>
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
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mark.lewis@mir3.com, lustig@brandeis.edu, dev@archonet.com
Subject: Re: Autovacuum running out of memory
In-Reply-To: <1192545195.6447.54.camel@archimedes>
* 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