Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com>
Cc: pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)
Date: 2014-11-26 13:35:36
Message-ID: 20141126133536.GM1639@alvin.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Maxim Boguk wrote:

> After careful examination of strace output I found one strange thing:
> constant flow of:
> 16:22:33.202523 read(3, 0x7fff4148a5b0, 16) = -1 EAGAIN (Resource
> temporarily unavailable)

Uh. What is on fd 3? (check /proc). If it's the stat socket, maybe
you're having network issues with localhost UDP connections or
something.

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Maxim Boguk 2014-11-26 14:02:05 Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)
Previous Message Maxim Boguk 2014-11-26 13:25:33 Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2014-11-26 13:37:46 Re: Follow up to irc on CREATE INDEX vs. maintenance_work_mem on 9.3
Previous Message Stephen Frost 2014-11-26 13:33:10 Re: superuser() shortcuts