Re: BUG #12071: Stat collector went crasy (50MB/s constant writes) - Mailing list pgsql-bugs

From Maxim Boguk
Subject Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)
Date
Msg-id CAK-MWwSnRjk-q_SNu+oOYwjU9fik5uXOez9v-v4Ua40aFjUNRA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-bugs
On Wed, Nov 26, 2014 at 4:35 PM, Alvaro Herrera <alvherre@2ndquadrant.com>
wrote:

> 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.
>

It's pipe to itself:
root@db13:~# ls -la /proc/26933/fd/ | grep 1343367616
lr-x------ 1 postgres postgres 64 Nov 26 16:54 3 -> pipe:[1343367616]
l-wx------ 1 postgres postgres 64 Nov 26 16:54 6 -> pipe:[1343367616]


--
Maxim Boguk
Senior Postgresql DBA
http://www.postgresql-consulting.ru/ <http://www.postgresql-consulting.com/>

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)
Next
From: Jamie Koceniak
Date:
Subject: Re: BUG #12050: Orphaned base files