From: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | Igor <igorya(dot)inscriptio(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument" |
Date: | 2012-11-18 17:36:40 |
Message-ID: | CAEYLb_VqQ+p-eR+hgbKHqu5Bocuim_G+F3pPyw5j8io7_Ar+yw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 18 November 2012 17:12, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> Ok, this is already helpful. Do you have anything the log that shows
> what process pid 95528 is? Could you grep for it?
I haven't looked at this in detail, but are you sure that this isn't
the bug that was fixed by commit
e81e8f9342b037246b284bad15e42e21b1929301 ? The "invalid argument"
poll() error is too generic to be sure what is really at fault, but
this doesn't need to be a FATAL error, it seems.
Is this a 32-bit platform? It's probably just that there is a large
number of sockets, which Google seems to think can cause this error
with poll(), so this seems like a slight variant of the problem
reported by Sean Chittenden (kernel resource exhaustion causes pipe
creation to fail, with unnecessarily bad consequences for Postgres).
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2012-11-18 17:41:23 | Re: BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument" |
Previous Message | Igor | 2012-11-18 17:33:38 | Re: BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument" |