Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id D10EB475D17 for ; Fri, 24 Jan 2003 22:10:30 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 16E1B475B33 for ; Fri, 24 Jan 2003 22:10:30 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h0P3AR5u001331; Fri, 24 Jan 2003 22:10:28 -0500 (EST) To: Stephan Szabo , Josh Berkus , Noah Silverman , pgsql-performance@postgresql.org Subject: Re: WEIRD CRASH?!?! In-reply-to: <28126.1043457126@sss.pgh.pa.us> References: <20030124162229.K38264-100000@megazone23.bigpanda.com> <28126.1043457126@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Fri, 24 Jan 2003 20:12:06 -0500" Date: Fri, 24 Jan 2003 22:10:27 -0500 Message-ID: <1330.1043464227@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/322 X-Sequence-Number: 969 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