pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Geoffrey <esoteric@3times25.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: John Allgood <john@turbocorp.com>
Cc: pgsql-admin@postgresql.org, Terry Lee Tucker <terry@leetuckert.net>
Cc: J. D. Pearson <jpearson@turbocorp.com>
Subject: Re: Out of file-descriptors message
Date: Thu, 30 Nov 2006 10:40:36 -0500
Message-ID: <456EFB74.2060902@3times25.net> (raw)
In-Reply-To: <13454.1164900627@sss.pgh.pa.us>
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>

Tom Lane wrote:
> Geoffrey <esoteric@3times25.net> 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



view thread (18+ messages)

Message-ID: <456EFB74.2060902@3times25.net>
Permalink:  ../456EFB74.2060902@3times25.net/
Also on:    postgresql.org/message-id/456EFB74.2060902@3times25.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: esoteric@3times25.net, tgl@sss.pgh.pa.us, john@turbocorp.com, terry@leetuckert.net, jpearson@turbocorp.com
  Subject: Re: Out of file-descriptors message
  In-Reply-To: <456EFB74.2060902@3times25.net>
  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> <456EFB74.2060902@3times25.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox