| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Daniel Andersen <zedar(at)free2air(dot)com(dot)au> |
| Cc: | "C(dot) Bensend" <benny(at)bennyvision(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Load problems... |
| Date: | 2001-12-19 05:48:23 |
| Message-ID: | 27036.1008740903@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Daniel Andersen <zedar(at)free2air(dot)com(dot)au> writes:
> [4059] DEBUG: connection startup failed (fork failure): Resource
> temporarily unavailable
> [4059] DEBUG: could not launch checkpoint process (fork failure): Resource
> temporarily unavailable
Hmm ... a fork failure suggests resource exhaustion somewhere in the
kernel. Do you have enough swap space? A large enough NFILE (kernel
filetable size) setting?
> there are generally up to 200 copies of postmaster running at any given time,
200 * a few dozen open files per backend is a lot of open files. I'm
betting on NFILE being the issue, myself.
Linuxen tend to lie through their teeth about the number of open files
they can support per-process (sysconf(_SC_OPEN_MAX)). In 7.2 you can
compensate for that by setting PG's config variable
max_files_per_process to something sane, maybe 50 to 100.
You'll still need to make sure that the kernel is configured to support
max_files_per_process * max_connections open files, but at least that's
a definable number now.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2001-12-19 06:02:43 | Re: Load problems... |
| Previous Message | Daniel Andersen | 2001-12-19 05:10:08 | Re: Load problems... |