From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephan Szabo <sszabo@megazone23.bigpanda.com>
To: Josh Berkus <josh@agliodbs.com>
To: Noah Silverman <noah@allresearch.com>
To: pgsql-performance@postgresql.org
Subject: Re: WEIRD CRASH?!?!
Date: Fri, 24 Jan 2003 22:10:27 -0500
Message-ID: <1330.1043464227@sss.pgh.pa.us> (raw)
In-Reply-To: <28126.1043457126@sss.pgh.pa.us>
References: <20030124162229.K38264-100000@megazone23.bigpanda.com>
<28126.1043457126@sss.pgh.pa.us>
I wrote:
> Hmm ... I wonder if Noah's machine could have been running out of kernel
> file table slots, or something like that? It does seem that it'd be
> more robust to use something like stat(2) to probe for an existing file.
I've applied a patch to do it that way in CVS HEAD. After examining the
code further I'm inclined not to risk back-patching it into 7.3, though.
xlog.c is full of open() calls that will elog(PANIC) if they fail, so
I think there was only a very small window of opportunity for Noah to
see this failure and not another one. The patch thus probably
contributes little real gain in reliability.
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, sszabo@megazone23.bigpanda.com, josh@agliodbs.com, noah@allresearch.com
Subject: Re: WEIRD CRASH?!?!
In-Reply-To: <1330.1043464227@sss.pgh.pa.us>
References: <20030124162229.K38264-100000@megazone23.bigpanda.com> <28126.1043457126@sss.pgh.pa.us> <1330.1043464227@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