From: Tom Lane <tgl@sss.pgh.pa.us>
To: C. Bensend <benny@bennyvision.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Memory exhausted in AllocSetAlloc
Date: Sun, 12 Sep 2004 01:43:09 -0400
Message-ID: <12799.1094967789@sss.pgh.pa.us> (raw)
In-Reply-To: <60549.63.227.74.41.1094956933.squirrel@63.227.74.41>
References: <60549.63.227.74.41.1094956933.squirrel@63.227.74.41>
"C. Bensend" <benny@bennyvision.com> writes:
> I understand what happened, but not exactly why - this machine is
> running with over 300M of RAM unused. Bumping this value down to 16M
> works fine. But why does it hit a memory exhausted error at 64M?
Maybe it's exceeding a ulimit setting?
You might want to watch it with "top" and see what size the process
actually gets to before failing. I'm not sure how accurate the
vacuum_mem throttle is ...
regards, tom lane
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: tgl@sss.pgh.pa.us, benny@bennyvision.com
Subject: Re: Memory exhausted in AllocSetAlloc
In-Reply-To: <12799.1094967789@sss.pgh.pa.us>
References: <60549.63.227.74.41.1094956933.squirrel@63.227.74.41> <12799.1094967789@sss.pgh.pa.us>
* 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