[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [GENERAL] freebsd + postgresql 8.3.3 = 100% of cpu usage on stats collector?
From:       Tom Lane <tgl () sss ! pgh ! pa ! us>
Date:       2008-06-30 15:15:42
Message-ID: 28740.1214838942 () sss ! pgh ! pa ! us
[Download RAW message or body]

hubert depesz lubaczewski <depesz@depesz.com> writes:
>  58241 postgres CALL  poll(0x7fffffffd4e0,0x1,0x7d0)
>  58241 postgres RET   poll -1 errno 4 Interrupted system call
>  58241 postgres CALL  poll(0x7fffffffd4e0,0x1,0x7d0)
>  58241 postgres RET   poll -1 errno 4 Interrupted system call
>  58241 postgres CALL  poll(0x7fffffffd4e0,0x1,0x7d0)
>  58241 postgres RET   poll -1 errno 4 Interrupted system call
>  58241 postgres CALL  poll(0x7fffffffd4e0,0x1,0x7d0)
>  58241 postgres RET   poll -1 errno 4 Interrupted system call
>  58241 postgres CALL  poll(0x7fffffffd4e0,0x1,0x7d0)
>  58241 postgres RET   poll -1 errno 4 Interrupted system call

Hmm.  The wait-for-input loop in the stats collector assumes that
if it gets EINTR, it should just retry the poll() call immediately.
Which AFAIK is correct.  I think you're looking at a kernel or libc
bug here --- somehow the EINTR failure is recurring continuously.
It's probably time to ask about this on a FreeBSD-specific list.

			regards, tom lane

-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
[prev in list] [next in list] [prev in thread] [next in thread]