| From: | Ken <mailinglists(at)creason(dot)com> | 
|---|---|
| To: | pgsql-general(at)postgresql(dot)org | 
| Subject: | Errors: Too many open files | 
| Date: | 2001-12-07 01:28:30 | 
| Message-ID: | 5.0.2.1.0.20011206171012.01be6c60@mail.fcs.net | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
During busy hours, Postgres and Apache are reporting
errors that there are too many open files, and sometimes 
Postgres will crash. I've searched all over for a way 
to increase this resource limit.
I have tried:
ulimit -n 8192 
(seems only to work for the current shell session)
echo "8192" > /proc/sys/fs/file-max 
(did not seem to make a difference)
adding this entry to /etc/security/limits.conf:
postgres        hard    nofile          4096
(did not seem to make a difference)
I have read the Postgres Administration docs 
"3.5.2 Resource Limits" but I am still unable to find
the solution.
Can anybody tell me how to increase the resource allocation,
and exactly where to make this change?
Any help would be greatly appreciated,
_Ken Creason
webmaster(at)fcs(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ken | 2001-12-07 02:17:25 | Re: Errors: Too many open files | 
| Previous Message | Andrew Snow | 2001-12-07 00:19:48 | Re: How to make a REALLY FAST db server? |