Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 12C109FA0FB for ; Thu, 30 Nov 2006 11:40:59 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 11411-09 for ; Thu, 30 Nov 2006 11:40:40 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from www.3times25.net (66-23-211-34.clients.speedfactory.net [66.23.211.34]) by postgresql.org (Postfix) with ESMTP id 9A1F39F9DAD for ; Thu, 30 Nov 2006 11:40:46 -0400 (AST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by www.3times25.net (Postfix) with ESMTP id 3538C54020; Thu, 30 Nov 2006 10:40:37 -0500 (EST) Message-ID: <456EFB74.2060902@3times25.net> Date: Thu, 30 Nov 2006 10:40:36 -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> <20061130142758.GI15105@alvh.no-ip.org> <456EEECC.1000701@3times25.net> <20061130145143.GJ15105@alvh.no-ip.org> <456EF08C.3000302@3times25.net> <13454.1164900627@sss.pgh.pa.us> In-Reply-To: <13454.1164900627@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/261 X-Sequence-Number: 23788 Tom Lane wrote: > Geoffrey writes: >> Alvaro Herrera wrote: >>> Yes. Which is kinda weird, because Postgres actually tests the number >>> when it starts, so that if you set the number too high, it will decrease >>> it according to what the kernel allows. >>> >>> Maybe the test is newer than the version you are running -- what was it, >>> again? >>> >> 7.4.13 > > Hmph ... 7.4.13 does have the same set_max_safe_fds() logic as HEAD. > So this shouldn't be happening really, no matter what the relative > values of max_files_per_process and ulimit -n are. > > Explanations I can think of: > > * ulimit -n decreased after process startup (is this even possible?) > > * something is leaking file descriptors that are outside fd.c's control, > such that eventually there are more than NUM_RESERVED_FDS of 'em. > > Theory B seems a lot more plausible. It'd be interesting to look at > "lsof" output for one of the backend processes that is emitting this > message, to see if we can identify what's getting leaked. We have been looking at a particular issue related to a library we've built into the backend. It does appear that this library could well be the culprit. We are researching it further, will post more as we get more info. -- Until later, Geoffrey Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. - Benjamin Franklin