From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Geoffrey <esoteric(at)3times25(dot)net> |
Cc: | John Allgood <john(at)turbocorp(dot)com>, pgsql-admin(at)postgresql(dot)org, Terry Lee Tucker <terry(at)leetuckert(dot)net>, "J(dot) D(dot) Pearson" <jpearson(at)turbocorp(dot)com> |
Subject: | Re: Out of file-descriptors message |
Date: | 2006-11-30 14:27:58 |
Message-ID: | 20061130142758.GI15105@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Geoffrey wrote:
> Alvaro Herrera wrote:
> >John Allgood wrote:
> >>Hey Tom
> >>
> >> I assume that if it is the kernel running out of descriptors that I
> >>would get the messages in dmesg. This message only appears in the log
> >>file for that database.
> >
> >Yeah, the point is that you have the max_files_per_process setting
> >higher than what the kernel likes. So decrease it, and Postgres will
> >adjust itself to use less file descriptors by closing and reopening
> >files as needed.
>
> I work with the original poster and wanted to make sure the problem here
> is clear.
Yes, that was understood from the beginning.
> The 'out of file descriptors' message is coming from
> Postgresql, not the kernel. Thus, it doesn't make sense to me that the
> max_files_per_process setting is too high. I would think we need to
> increase it so that Postgresql will stop generating these errors.
No, you need to lower it so that Postgres doesn't _try_ to use as many
file descriptors. Read this again:
> > So decrease it, and Postgres will
> >adjust itself to use less file descriptors by closing and reopening
> >files as needed.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Geoffrey | 2006-11-30 14:46:36 | Re: Out of file-descriptors message |
Previous Message | Geoffrey | 2006-11-30 14:26:52 | Re: Out of file-descriptors message |