| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | Daniel Andersen <zedar(at)free2air(dot)com(dot)au> |
| Cc: | <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Load problems... |
| Date: | 2001-12-19 06:02:43 |
| Message-ID: | 20011218215658.O67016-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> sort_mem = 1024
> shared_buffers = 2048 (tried higher, but didnt' seem to improve anything)
> max_connections = 300
>
> error message just comes out of the blue, the database is chugging along
> happily and then suddenly[4059] DEBUG: connection startup failed (fork
> failure): Resource temporarily unavailable
> [4059] DEBUG: connection startup failed (fork failure): Resource
> temporarily unavailable
> [4059] DEBUG: could not launch checkpoint process (fork failure): Resource
> temporarily unavailable
> [4059] DEBUG: connection startup failed (fork failure): Resource
> temporarily unavailable
> [4059] DEBUG: connection startup failed (fork failure): Resource
> temporarily unavailable
Sounds like fork returning EAGAIN.
What does ulimit -a show for the postgres user?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lamar Owen | 2001-12-19 06:11:03 | Re: Load problems... |
| Previous Message | Tom Lane | 2001-12-19 05:48:23 | Re: Load problems... |