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
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.
Good guess. Freebsd 4.8 or so.
Chris
---(end of broadcast)---
On Fri, May 13, 2005 at 09:45:15AM +0800, Christopher Kings-Lynne wrote:
> A few days back the load increased on our database server to the point
> where it could not get enough file handles. This causes the backends to
> crash, get restarted only to crash again, on and on.
>
> We fixed it by
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> A few days back the load increased on our database server to the point
> where it could not get enough file handles. This causes the backends to
> crash, get restarted only to crash again, on and on.
> We fixed it by bumping kern.maxfiles, b
A few days back the load increased on our database server to the point
where it could not get enough file handles. This causes the backends to
crash, get restarted only to crash again, on and on.
We fixed it by bumping kern.maxfiles, but was just wondering if this is
a scenario that PostgreSQL
Hi,
A few days back the load increased on our database server to the point
where it could not get enough file handles. This causes the backends to
crash, get restarted only to crash again, on and on.
We fixed it by bumping kern.maxfiles, but was just wondering if this is
a scenario that Postgr
