Re: Vacuum of large tables causing replication delays to hot standby

From: Jeff Mcdowell <Jeff(dot)Mcdowell(at)panerabread(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-general(at)postgreSQL(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Vacuum of large tables causing replication delays to hot standby
Date: 2016-04-30 19:03:02
Message-ID: 93F1623A-31D9-4BDF-9E17-DC20BF10B184@panerabread.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

9.2.12

Sent from my iPhone

> On Apr 30, 2016, at 12:37 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Jeff Mcdowell <Jeff(dot)Mcdowell(at)panerabread(dot)com> writes:
>> 95% of the time, the delay is only microseconds. But we have discovered that whenever the master does an auto vacuum of a large table, the transaction replay delay can climb is high as 1 hour. These delays don’t seem to correlate with any particular queries that are running against the master or the standby, and the delay only subsides when the vacuum completes.
>
> What PG version might this be?
>
> regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Stephen Cook 2016-05-01 02:04:19 Re: Skip trigger?
Previous Message Alvaro Herrera 2016-04-30 17:45:42 Re: Vacuum of large tables causing replication delays to hot standby