| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Brian Hirt <bhirt(at)mobygames(dot)com> |
| Cc: | Joe Lester <joe_lester(at)sweetwater(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Increasing Max Connections Mac OS 10.3 |
| Date: | 2004-02-10 18:30:23 |
| Message-ID: | 24989.1076437823@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Brian Hirt <bhirt(at)mobygames(dot)com> writes:
> ... after i did ulimit -n
> unlimited the problem joe describes went away for me.
Hmm. Postgres assumes it can use the smaller of max_files_per_process
and sysconf(_SC_OPEN_MAX). From what you describe, I suspect that OSX's
sysconf call ignores the "ulimit -n" restriction and thus encourages us
to think we can use more than we really can. If that's the correct
explanation then the LOG messages are just a cosmetic problem (as long
as kern.maxfiles comfortably exceeds max_connections times ulimit -n).
I wonder whether we should also probe getrlimit(RLIMIT_NOFILE)? Anyone
have an idea whether that returns different limits than sysconf()?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Siracusa | 2004-02-10 18:38:04 | Re: Increasing Max Connections Mac OS 10.3 |
| Previous Message | Brian Hirt | 2004-02-10 18:15:33 | Re: Increasing Max Connections Mac OS 10.3 |