Skip site navigation (1) Skip section navigation (2)

Re:

From: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
To: jallgood(at)the-allgoods(dot)net
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re:
Date: 2006-09-13 06:35:03
Message-ID: 20060913063503.GB23173@nasby.net (view raw or flat)
Thread:
Lists: pgsql-performance
On Tue, Sep 12, 2006 at 03:33:08PM -0400, jallgood(at)the-allgoods(dot)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(at)nasby(dot)net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)

In response to

  • at 2006-09-12 19:33:08 from jallgood

pgsql-performance by date

Next:From: Jim C. NasbyDate: 2006-09-13 06:41:52
Subject: Re: Performance With Joins on Large Tables
Previous:From: Mischa SandbergDate: 2006-09-13 00:51:27
Subject: Re: Bad plan for join to aggregate of join.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group