Re: Vacuum causing crashes

From: Douglas McNaught <doug(at)mcnaught(dot)org>
To: David Mitchell <david(dot)mitchell(at)telogis(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Vacuum causing crashes
Date: 2005-06-23 23:30:09
Message-ID: m2wtokbqim.fsf@Douglas-McNaughts-Powerbook.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

David Mitchell <david(dot)mitchell(at)telogis(dot)com> writes:

> Hi,
>
> We're running a Postgres 8.0.1 database and have a maintenance process
> that runs vacuum on selected tables every 10 minutes. Each table takes
> around 2-3 seconds to vacuum. Since we've started this process we've
> seen a lot of postmaster crashes (it says it received signal 9). It
> appears these crashes occur when we try to stop a vacuum by
> interrupting the vacuumdb process, but sometimes they occur without us
> having to do this.
>
> Any ideas? We didn't experience so many database crashes before we
> started vacuuming regularly.

If you're running Linux, it's possible that your system is
overcommitted and low on memory and the kernel is picking random
processes to kill. There should be entries in the syslogs related to
this, if that's what's happening. There are ways to tell (some
versions of) Linux not to overcommit memory.

Otherwise, no part of Postgres sends signal 9 AFAIK, so it's either a
rogue script or a person doing the killing.

-Doug

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2005-06-24 01:18:15 Re: Postmaster Out of Memory
Previous Message David Mitchell 2005-06-23 22:55:06 Vacuum causing crashes