Re: Re: Too many open files (was Re: spinlock problems reported earlier) - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Re: Too many open files (was Re: spinlock problems reported earlier)
Date
Msg-id Pine.LNX.4.30.0012240000020.799-100000@peter.localdomain
Whole thread Raw
In response to Re: Re: Too many open files (was Re: spinlock problems reported earlier)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: Too many open files (was Re: spinlock problems reported earlier)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane writes:

> I'm not sure why this didn't get dealt with, but I think it's a "must
> fix" kind of problem for 7.1.  The dbadmin has *got* to be able to
> limit Postgres' appetite for open file descriptors.

Use ulimit.

> I propose we add a new configuration parameter, MAX_FILES_PER_PROCESS,
> with a default value of about 100.  A new backend would set its
> max-files setting to the smaller of this parameter or
> sysconf(_SC_OPEN_MAX).

I think this is an unreasonable interference with the customary operating
system interfaces (e.g., ulimit).  The last thing I want to hear is
"Postgres is slow and it only opens 100 files per process even though I
<did something> to allow 32 million."

-- 
Peter Eisentraut      peter_e@gmx.net       http://yi.org/peter-e/



pgsql-hackers by date:

Previous
From: mlw
Date:
Subject: Re: Too many open files (was Re: spinlock problems reported earlier)
Next
From: Tom Lane
Date:
Subject: Re: Re: Too many open files (was Re: spinlock problems reported earlier)