| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL running out of file handles |
| Date: | 2005-05-13 03:27:11 |
| Message-ID: | 42841E8F.10605@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I suppose you are running on some BSD variant? BSD is notorious for
> promising more than it can deliver with respect to number of open files
> per process. This is a kernel bug, not a Postgres bug.
>
> You can adjust Postgres' max_files_per_process setting to compensate for
> the kernel's lying about its capabilities.
>
> (Postgres is in fact one of the most robust applications I know of
> in terms of not going belly-up in response to EMFILE or ENFILE.
> However, if there are not any spare descriptors to close, there's
> not a lot we can do except fail.)
>
> regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2005-05-13 03:27:35 | Re: PostgreSQL running out of file handles |
| Previous Message | Tom Lane | 2005-05-13 03:20:35 | Re: PostgreSQL running out of file handles |