From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | "Jason Lustig" <lustig(at)brandeis(dot)edu> |
Cc: | "Richard Huxton" <dev(at)archonet(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Autovacuum running out of memory |
Date: | 2007-10-16 14:22:54 |
Message-ID: | dcc563d10710160722i7ea8d14ds2c526519f767cddb@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 10/16/07, Jason Lustig <lustig(at)brandeis(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-10-16 14:26:08 | Re: Vacuum goes worse |
Previous Message | Richard Huxton | 2007-10-16 14:22:35 | Re: Autovacuum running out of memory |