Обсуждение: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

The following bug has been logged on the website:

Bug reference:      7545
Logged by:          Len Tanaka
Email address:      tanakalen@gmail.com
PostgreSQL version: 9.2.0
Operating system:   Mac OS X 10.6.8
Description:        =


Multiple log files with same error repeated:
poll() failed: Invalid argument

Prior to error, in user account in user table doing an insert that has not
failed in past. Unresponsive thereafter. Unable to shutdown postmaster.

configure:
./configure --with-includes=3D/sw/include --with-libraries=3D/sw/lib --with=
-perl
--with-python --with-openssl --with-bonjour --with-pam --with-krb5
--with-ldap --enable-thread-safety --with-libxml --with-libxslt
--enable-dtrace

make check passed all tests.

Thanks for any help, reverted to 9.1.5 and no similar problem.

Len

Excerpts from tanakalen's message of lun sep 17 06:00:05 -0300 2012:
> The following bug has been logged on the website:
>=20
> Bug reference:      7545
> Logged by:          Len Tanaka
> Email address:      tanakalen@gmail.com
> PostgreSQL version: 9.2.0
> Operating system:   Mac OS X 10.6.8
> Description:       =20
>=20
> Multiple log files with same error repeated:
> poll() failed: Invalid argument
>=20
> Prior to error, in user account in user table doing an insert that has =
not
> failed in past. Unresponsive thereafter. Unable to shutdown postmaster.
>=20
> configure:
> ./configure --with-includes=3D/sw/include --with-libraries=3D/sw/lib --=
with-perl
> --with-python --with-openssl --with-bonjour --with-pam --with-krb5
> --with-ldap --enable-thread-safety --with-libxml --with-libxslt
> --enable-dtrace

So the full log files correspond to the server log file, right?  What
process is filling the logs?  (You can tell by adding a %p to
log_line_prefix in postgresql.conf, if it's not there already).

Is the table a FDW table or something otherwise funny?  Please give more
details; also about the underlying platform (is this a non-Intel
dinosaur or something?)

--=20
=C3=81lvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

Excerpts from Len Tanaka's message of jue sep 27 18:01:30 -0300 2012:
> Thank you for getting back. I noticed an update to 9.2.1. Will add log
> parameter and apply update. DB is not a particularly complex table and
> no foreign wrapping. Machine is older core duo though running OS X
> 10.6.8.
>=20
> Hope problem fixed with update.=20

I don't think we fixed any portability bugs in poll() usage in 9.2.1.

> If recurs, should I resubmit bug report? Or will this remain open?

This one remains open.  Just make sure you reply by email and CC
pgsql-bugs@postgresql.org.

--=20
=C3=81lvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

Both 9.2.1 and .2 seem to have fixed this issue. Running for over a month no=
w without recurrence.
Thank you for your help. Happy holidays.
Len



On Sep 27, 2012, at 6:00 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote=
:

> Excerpts from Len Tanaka's message of jue sep 27 18:01:30 -0300 2012:
>> Thank you for getting back. I noticed an update to 9.2.1. Will add log
>> parameter and apply update. DB is not a particularly complex table and
>> no foreign wrapping. Machine is older core duo though running OS X
>> 10.6.8.
>>=20
>> Hope problem fixed with update.
>=20
> I don't think we fixed any portability bugs in poll() usage in 9.2.1.
>=20
>> If recurs, should I resubmit bug report? Or will this remain open?
>=20
> This one remains open.  Just make sure you reply by email and CC
> pgsql-bugs@postgresql.org.
>=20
> --=20
> =C3=81lvaro Herrera                http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training & Services