Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id B5ED69F9DAD for ; Thu, 30 Nov 2006 10:47:01 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 33875-03 for ; Thu, 30 Nov 2006 10:46:40 -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 6260C9F9C9E for ; Thu, 30 Nov 2006 10:46:40 -0400 (AST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by www.3times25.net (Postfix) with ESMTP id 2613E54022; Thu, 30 Nov 2006 09:46:37 -0500 (EST) Message-ID: <456EEECC.1000701@3times25.net> Date: Thu, 30 Nov 2006 09:46:36 -0500 From: Geoffrey User-Agent: Thunderbird 1.5.0.8 (X11/20061025) MIME-Version: 1.0 To: Geoffrey , 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> <20061130142758.GI15105@alvh.no-ip.org> In-Reply-To: <20061130142758.GI15105@alvh.no-ip.org> 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/253 X-Sequence-Number: 23780 Alvaro Herrera wrote: > Geoffrey wrote: >> Alvaro Herrera wrote: >>> John Allgood wrote: >>>> Hey Tom >>>> >>>> I assume that if it is the kernel running out of descriptors that I >>>> would get the messages in dmesg. This message only appears in the log >>>> file for that database. >>> Yeah, the point is that you have the max_files_per_process setting >>> higher than what the kernel likes. So decrease it, and Postgres will >>> adjust itself to use less file descriptors by closing and reopening >>> files as needed. >> I work with the original poster and wanted to make sure the problem here >> is clear. > > Yes, that was understood from the beginning. > >> 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. > > No, you need to lower it so that Postgres doesn't _try_ to use as many > file descriptors. Read this again: > >>> So decrease it, and Postgres will >>> adjust itself to use less file descriptors by closing and reopening >>> files as needed. Okay, I'm just not getting it. Postgres complains that it is out of file descriptors. The kernel is not complaining about any such issues. So I should lower the max_files_per_process value and this will rid us of the 'out of file descriptors' error? Is it because the max_files_per_process is greater then the number of file descriptors that are alloted to Postgres by the kernel? -- Until later, Geoffrey Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. - Benjamin Franklin