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:29:19 -0500
Message-ID: <456EF8CF.6040809@3times25.net> (raw)
In-Reply-To: <13195.1164899425@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>
	<13195.1164899425@sss.pgh.pa.us>

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



view thread (18+ messages)  latest in thread

Message-ID: <456EF8CF.6040809@3times25.net>
Permalink:  ../456EF8CF.6040809@3times25.net/
Also on:    postgresql.org/message-id/456EF8CF.6040809@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: <456EF8CF.6040809@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> <13195.1164899425@sss.pgh.pa.us> <456EF8CF.6040809@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