From: Scott Marlowe <scott.marlowe@gmail.com>
To: Geoffrey <lists@serioustechnology.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: vacuum killed because of out of memory
Date: Wed, 29 Aug 2007 12:43:50 -0500
Message-ID: <dcc563d10708291043o60270ca1yadff1e2dc9136f52@mail.gmail.com> (raw)
In-Reply-To: <46D2DBF6.609@serioustechnology.com>
References: <46D2DBF6.609@serioustechnology.com>
On 8/27/07, Geoffrey <lists@serioustechnology.com> wrote:
> I've recently reviewed the various recent threads on out of memory
> problems. We just had a similar issue last night. We have 11
> postmasters running on two machines in a cluster environment. Five on
> one, six on the other. They've been running in this manner for a little
> over a year now.
> So, my question is, based on the configuration of this box and the
> configuration of postgresql, can anyone point to anything that might
> cause this to happen?
Too high a setting for maint_work_mem
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-admin@postgresql.org
Cc: scott.marlowe@gmail.com, lists@serioustechnology.com
Subject: Re: vacuum killed because of out of memory
In-Reply-To: <dcc563d10708291043o60270ca1yadff1e2dc9136f52@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