Re: Hot Standby performance issue

From: Tomas Vondra <tv(at)fuzzy(dot)cz>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Hot Standby performance issue
Date: 2013-11-02 19:40:23
Message-ID: 52755527.7000902@fuzzy.cz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 28.10.2013 21:23, sparikh wrote:
> Hi,
>
> Yes, you are right. The table is the biggest one . Please find below the
> information you requested. I agree the fact that autovacuum ran on this
> table would fix the performance issue on standby does not sound very
> convincing. But that is the only thing I could correlate when the query on
> standby started working again. Otherwise there is absolutely no changes at
> code level , database level or OS level.
> As of now query is still working fine on standby.
>
> I may be wrong, but could it be the case that standby disk was too much
> fragmented compare to primary and autovaccum on primary fixed that.
> (Assuming autovacuum on primary internally triggers the same on standby)

I find it very unlikely, but you didn't gave us necessary data (say, how
much free space was on the disks, etc.). The best way to pinpoint the
issue would be to run some profiler (which we have repeatedly asked you
to do), but now that the issue disappeared we can only guess.

Please monitor the system and if it happens again run perf or other
profiler so that we know where the time is spent.

Tomas

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Caio Casimiro 2013-11-03 22:05:16 Slow index scan on B-Tree index over timestamp field
Previous Message Tomas Vondra 2013-11-02 19:33:53 Re: Hot Standby performance issue