| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Noah Silverman <noah(at)allresearch(dot)com> |
| Cc: | Rod Taylor <rbt(at)rbt(dot)ca>, Postgresql Performance <pgsql-performance(at)postgresql(dot)org>, josh(at)agliodbs(dot)com |
| Subject: | Re: WEIRD CRASH?!?! |
| Date: | 2003-01-25 01:38:44 |
| Message-ID: | 28320.1043458724@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Noah Silverman <noah(at)allresearch(dot)com> writes:
> It actually looks like the problem was with file descriptors. Our
> shell only had 1024 set, and we also have mysql running and using up a
> bunch of those. We just upped to limit to 8000 to see it that would
> give postgres more room to breathe.
Ah-hah. You might also want to set max_files_per_process (in
postgresql.conf) to something small enough to ensure Postgres can't run
you out of descriptors. Linux has a bad habit of promising more than
it can deliver when Postgres asks how many FDs are okay to use. The
max_files_per_process setting is useful to prevent Postgres from
believing whatever fairy-tale sysconf(3) tells it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Brown | 2003-01-25 02:11:59 | Re: Mount options for Ext3? |
| Previous Message | Tom Lane | 2003-01-25 01:29:41 | Re: Having trouble with backups (was: Re: Crash Recovery) |