Bruno Wolff III <bruno@wolff.to> writes: > It sounds like what is really happening is that > you are hitting an OS limit on the number of open files. You should be > able to increase that limit. There have also been some discussions about > postgres doing a better job of telling when it has opened too many files > within the last several months. I don't remember much about the details > of the change or which version they were applied to. If I recall that change correctly, it was prompted by the discovery that on OS X we were drastically underestimating the number of open file descriptors sucked up per backend. (OS X treats each semaphore as an open file, so there are about max_connections open files per process that we weren't accounting for.) I think it is just in CVS tip and not yet in any released version. For the moment the answer is to size your kernel file table on the assumption that you need about max_connections * (max_files_per_process + max_connections) filetable slots just for Postgres, plus whatever you want available for the rest of the system. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
