Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 15E669FA18B for ; Thu, 30 Nov 2006 11:29:41 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 25340-03-2 for ; Thu, 30 Nov 2006 11:29:19 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from www.3times25.net (duck.3times25.net [66.23.211.34]) by postgresql.org (Postfix) with ESMTP id 318C99F9DAD for ; Thu, 30 Nov 2006 11:29:25 -0400 (AST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by www.3times25.net (Postfix) with ESMTP id C35AC54020; Thu, 30 Nov 2006 10:29:19 -0500 (EST) Message-ID: <456EF8CF.6040809@3times25.net> Date: Thu, 30 Nov 2006 10:29:19 -0500 From: Geoffrey User-Agent: Thunderbird 1.5.0.8 (X11/20061025) MIME-Version: 1.0 To: Tom Lane CC: John Allgood , pgsql-admin@postgresql.org, Terry Lee Tucker , "J. D. Pearson" Subject: Re: Out of file-descriptors message References: <456DF2DE.3060002@turbocorp.com> <4727.1164835974@sss.pgh.pa.us> <456E03C9.6070204@the-allgoods.net> <20061129222523.GI7001@alvh.no-ip.org> <456EE6CE.2030106@3times25.net> <13195.1164899425@sss.pgh.pa.us> In-Reply-To: <13195.1164899425@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/259 X-Sequence-Number: 23786 Tom Lane wrote: > Geoffrey writes: >> I work with the original poster and wanted to make sure the problem here >> is clear. The 'out of file descriptors' message is coming from >> Postgresql, not the kernel. Thus, it doesn't make sense to me that the >> max_files_per_process setting is too high. I would think we need to >> increase it so that Postgresql will stop generating these errors. > > These are not "errors", they are only log messages. It would be > perfectly safe to ignore them. However, as Alvaro says, if you want > to get rid of them then the way to do that is to *decrease* > max_files_per_process to something less than whatever per-process file > limit the kernel is enforcing. Understood, but we had one database that was generating these messages continuously over a period of 4 days. Eventually, the machine became unresponsive. Still, we did not have any file descriptor errors generated by the kernel. Thus we are considering whether we should decrease max_files_per_process or increase the postgres id's 'ulimit -n' value. -- Until later, Geoffrey Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. - Benjamin Franklin