Re: freebsd + postgresql 8.3.3 = 100% of cpu usage on stats collector?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: depesz(at)depesz(dot)com
Cc: Bill Moran <wmoran(at)collaborativefusion(dot)com>, Rodrigo Gonzalez <rjgonzale(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: freebsd + postgresql 8.3.3 = 100% of cpu usage on stats collector?
Date: 2008-06-30 15:15:42
Message-ID: 28740.1214838942@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

hubert depesz lubaczewski <depesz(at)depesz(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2008-06-30 15:19:55 Re: server log files
Previous Message Tom Lane 2008-06-30 14:51:36 Re: "out of balance" result on select from suspected index corruption