pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <scott.marlowe@gmail.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 09:22:54 -0500
Message-ID: <dcc563d10710160722i7ea8d14ds2c526519f767cddb@mail.gmail.com> (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 10/16/07, Jason Lustig <lustig@brandeis.edu> wrote:
> I ran "ulimit -a" for the postgres user, and here's what I got:
>
> core file size          (blocks, -c) 200000
> data seg size           (kbytes, -d) 200000
> max nice                        (-e) 0
> file size               (blocks, -f) unlimited
> pending signals                 (-i) 32635
> max locked memory       (kbytes, -l) 32
> max memory size         (kbytes, -m) 200000
> open files                      (-n) 100
> pipe size            (512 bytes, -p) 8
> POSIX message queues     (bytes, -q) 819200
> max rt priority                 (-r) 0
> stack size              (kbytes, -s) 8192
> cpu time               (seconds, -t) unlimited
> max user processes              (-u) 100
> virtual memory          (kbytes, -v) 200000
> file locks                      (-x) unlimited

There ya go.  it's limited to 200M memory.

Generally speaking, limiting postgresql to something that small is not
a good idea.  Set it to ~ 1 Gig or so and see how it works.



view thread (22+ messages)  latest in thread

Message-ID: <dcc563d10710160722i7ea8d14ds2c526519f767cddb@mail.gmail.com>
Permalink:  ../dcc563d10710160722i7ea8d14ds2c526519f767cddb@mail.gmail.com/
Also on:    postgresql.org/message-id/dcc563d10710160722i7ea8d14ds2c526519f767cddb@mail.gmail.com

 · 

reply

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: scott.marlowe@gmail.com, lustig@brandeis.edu, dev@archonet.com
  Subject: Re: Autovacuum running out of memory
  In-Reply-To: <dcc563d10710160722i7ea8d14ds2c526519f767cddb@mail.gmail.com>

* 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