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

Re: Re: Too many open files (was Re: spinlock problems reported earlier)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: Too many open files (was Re: spinlock problems reported earlier)
Date: 2000-12-24 03:58:10
Message-ID: 27652.977630290@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
>> 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).

> Seems nice idea. We have been heard lots of problem reports caused by
> ruuning out of the file table.

> However it would be even nicer, if it could be configurable at runtime
> (at the postmaster starting up time) like -N option.

Yes, what I meant was a GUC parameter named MAX_FILES_PER_PROCESS.
You could set it via postmaster.opts or postmaster command line switch.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Brent VernerDate: 2000-12-24 04:49:40
Subject: Re: 7.1 on DEC/Alpha
Previous:From: Mike S. AvelarDate: 2000-12-24 03:13:03
Subject: Java and Postgresql

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