Peter Geoghegan <pe...@2ndquadrant.com> writes: > 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.
He's running BSD, which is not at all wishy-washy about what it means: [EINVAL] The specified time limit is negative. The reason it's FATAL is that it's happening in the syslogger process, which has no error recovery capability. regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs