From: | Steve Atkins <steve(at)blighty(dot)com> |
---|---|
To: | pgsql-general General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: How many file descriptors does postgres need? |
Date: | 2010-03-09 15:47:56 |
Message-ID: | C630BE64-6331-4CE8-858C-92FCFDE4562F@blighty.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mar 9, 2010, at 5:11 AM, Royce Ausburn wrote:
> G'day all,
>
> We recently had a bit of a catastrophe when one of our postgres databases opened too many files. It was a reasonably easy fix, but it did get me thinking. Is there a rule of thumb in determining how many file descriptors should be available to a postgres database/cluster?
>
> I'd be happy to set it to some large number, but I'd really like some confidence about how much the database can grow with a new limit.
Postgresql is supposed to cope with file descriptor limits quite happily, as long as the OS actually restricts the number of files a process can have open. If it doesn't restrict the number, just falls over if there's too many, there's a postgresql configuration option to limit it (max_files_per_process, I think).
What OS are you on, and what was the catastrophe?
Cheers,
Steve
From | Date | Subject | |
---|---|---|---|
Next Message | Steve T | 2010-03-09 15:55:54 | Re: Urgent help needed- alias name in update statement |
Previous Message | Scot Kreienkamp | 2010-03-09 15:46:41 | Re: autovacuum question |