Re: BUG #8192: On very large tables the concurrent update with vacuum lag the hot_standby replica - Mailing list pgsql-bugs

From Jeff Janes
Subject Re: BUG #8192: On very large tables the concurrent update with vacuum lag the hot_standby replica
Date
Msg-id CAMkU=1xxuQM2D18AKhGyfFWP4s2B9cdjbNORzA-3pqTtYpu7mA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #8192: On very large tables the concurrent update with vacuum lag the hot_standby replica  (Federico Campoli <federico@brandwatch.com>)
Responses Re: BUG #8192: On very large tables the concurrent update with vacuum lag the hot_standby replica
List pgsql-bugs
On Tue, Jun 4, 2013 at 8:36 AM, Federico Campoli <federico@brandwatch.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

pgsql-bugs by date:

Previous
From: Jeff Janes
Date:
Subject: Re: BUG #8192: On very large tables the concurrent update with vacuum lag the hot_standby replica
Next
From: Tom Lane
Date:
Subject: Re: BUG #8215: pg_dump includes table out of order in SQL dump