Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 5217E475B33 for ; Fri, 24 Jan 2003 20:38:43 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 8F2F7475461 for ; Fri, 24 Jan 2003 20:38:42 -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 h0P1ci5u028321; Fri, 24 Jan 2003 20:38:44 -0500 (EST) To: Noah Silverman Cc: Rod Taylor , Postgresql Performance , josh@agliodbs.com Subject: Re: WEIRD CRASH?!?! In-reply-to: <4E61F6E7-3002-11D7-A3A3-000393AA8F3C@allresearch.com> References: <4E61F6E7-3002-11D7-A3A3-000393AA8F3C@allresearch.com> Comments: In-reply-to Noah Silverman message dated "Fri, 24 Jan 2003 20:14:09 -0500" Date: Fri, 24 Jan 2003 20:38:44 -0500 Message-ID: <28320.1043458724@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/317 X-Sequence-Number: 964 Noah Silverman 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