From: Tom Lane <tgl@sss.pgh.pa.us>
To: Noah Silverman <noah@allresearch.com>
Cc: Rod Taylor <rbt@rbt.ca>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Cc: josh@agliodbs.com
Subject: Re: WEIRD CRASH?!?!
Date: Fri, 24 Jan 2003 20:38:44 -0500
Message-ID: <28320.1043458724@sss.pgh.pa.us> (raw)
In-Reply-To: <4E61F6E7-3002-11D7-A3A3-000393AA8F3C@allresearch.com>
References: <4E61F6E7-3002-11D7-A3A3-000393AA8F3C@allresearch.com>
Noah Silverman <noah@allresearch.com> writes:
> It actually looks like the problem was with file descriptors. Our
> shell only had 1024 set, and we also have mysql running and using up a
> bunch of those. We just upped to limit to 8000 to see it that would
> give postgres more room to breathe.
Ah-hah. You might also want to set max_files_per_process (in
postgresql.conf) to something small enough to ensure Postgres can't run
you out of descriptors. Linux has a bad habit of promising more than
it can deliver when Postgres asks how many FDs are okay to use. The
max_files_per_process setting is useful to prevent Postgres from
believing whatever fairy-tale sysconf(3) tells it.
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-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, noah@allresearch.com, rbt@rbt.ca, josh@agliodbs.com
Subject: Re: WEIRD CRASH?!?!
In-Reply-To: <28320.1043458724@sss.pgh.pa.us>
References: <4E61F6E7-3002-11D7-A3A3-000393AA8F3C@allresearch.com> <28320.1043458724@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