From: Bradley Kieser <brad@kieser.net>
To: PgSQL ADMIN <pgsql-admin@postgresql.org>
Subject: Postgres kills machine
Date: Sun, 09 Jan 2005 14:31:54 +0000
Message-ID: <41E1405A.1060603@kieser.net> (raw)
Periodically we have queries (can't log in to see which ones) that kill
our machine by consuming huge amounts of resource. I thought that I had
fixed this by writing a cron job that vacuums all the databases every
night, but today our machine froze again.
We run PG on Linux, for the machine in question is it Mandrake 10.0.
The errors in the syslog are all to do with VM, so I assume that we are
running out of RAM. There is 1.5GB of RAM in the box which should be
more than enough for the databases that we run.
I know that I can set process limits in the limits.conf file, but can
anyone suggest sensible values to put in there to limit the max memory
to 200MB per pg process?
I have read that limits.conf only works if PG is linked using PAM and
someone in a thread said that PG doesn't use PAM. Can someone please
advise me on this?
Thanks,
Brad
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: brad@kieser.net
Subject: Re: Postgres kills machine
In-Reply-To: <41E1405A.1060603@kieser.net>
References: <41E1405A.1060603@kieser.net>
* 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