From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
---|---|
To: | lincoln(dot)spiteri(at)st(dot)com |
Cc: | pgman(at)candle(dot)pha(dot)pa(dot)us, serge(at)globalbeach(dot)com, pgsql-general(at)postgreSQL(dot)org |
Subject: | Re: open pgsql files (was Re: [GENERAL] Mime-Version: 1.0) |
Date: | 2000-02-29 01:17:31 |
Message-ID: | 20000229101731R.t-ishii@sra.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> Even after extending the number of file descriptors on the kernel quite
> significantly I still get the occasional crash due to too many open files. I
> would say that the current ploicy is too aggressive uder heavy loads.
>> This actually brings up a good point. We currently cache all
>> descriptors up to the limit the OS will allow for a process.
>>
>> Is this too aggressive? Should we limit it to 50% of the maximum?
We could limit the number of open files/per backend by using limit, or
ulimit etc. if all file accesses would go through Vfd. Is there any
reason to use open() directly, for example, in mdblindwrt()?
Also, I have noticed that some files such as pg_internal.init are not
necessary kept open and should be closed after we finish to use it to
save a fd.
--
Tatsuo Ishii
From | Date | Subject | |
---|---|---|---|
Next Message | Jose Soares | 2000-02-29 13:37:12 | Re: [GENERAL] CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP |
Previous Message | sheila bel | 2000-02-29 00:51:46 | CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP |