Date: Wed, 13 Sep 2006 01:35:03 -0500
From: "Jim C. Nasby" <jim@nasby.net>
To: jallgood@the-allgoods.net
Cc: pgsql-performance@postgresql.org
Subject: Re: 
Message-ID: <20060913063503.GB23173@nasby.net>
References: <4307021.595181158089587924.JavaMail.servlet@perfora>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4307021.595181158089587924.JavaMail.servlet@perfora>
User-Agent: Mutt/1.5.11

On Tue, Sep 12, 2006 at 03:33:08PM -0400, jallgood@the-allgoods.net wrote:
> Hello All
> 
> I am getting this message in my log files for my database.
>  
> LOG: out of file descriptors: Too many open files; release and retry.
> 
> At some point the memomy didn't get released and the postmaster reset itself terminating all client connections. I am not sure what direction to go. I can increase the file-max in the kernel but it looks reasonably sized already . Or decrease the max_file_per_process. Has anyone on the list encountered this issue. I am running Postgres 7.4.7.

PostgreSQL could be using somewhere around as much as
max_files_per_process * ( max_connections + 5 ), so make sure that
matches file-max (the + 5 is because there are non-connection processes
such as the bgwriter).

If that looks OK, some file descriptors might have been left around from
the crash... I know this can happen with shared memory segments. It
normally won't happen with file descriptors, but perhaps it is possible.
If that's the case, a reboot would certainly fix it.

BTW, you should upgrade to the latest 7.4 release.
-- 
Jim Nasby                                            jim@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)