Re: BUG #8192: On very large tables the concurrent update with vacuum lag the hot_standby replica

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Federico Campoli <federico(at)brandwatch(dot)com>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #8192: On very large tables the concurrent update with vacuum lag the hot_standby replica
Date: 2013-06-06 20:22:26
Message-ID: CAMkU=1xxuQM2D18AKhGyfFWP4s2B9cdjbNORzA-3pqTtYpu7mA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Jun 4, 2013 at 8:36 AM, Federico Campoli <federico(at)brandwatch(dot)com>wrote:

>
> This is the gprof output for the profile.
>

This looks to me like the gprof of a process that is either idle, or
completely IO bound.

I'd probably approach this with a combination of "strace -T -ttt -p <PID>"
and "lsof -p <PID>" on the PID of the start-up process, to see which file
descriptors it is waiting for read or writes on, and what the underlying
names of the files for those file descriptors are.

Cheers,

Jeff

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2013-06-06 22:02:55 Re: BUG #8215: pg_dump includes table out of order in SQL dump
Previous Message Jeff Janes 2013-06-06 20:17:48 Re: BUG #8192: On very large tables the concurrent update with vacuum lag the hot_standby replica