pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedReplica lag, high read IO, vacuum index scanning bug?
2+ messages / 2 participants
[nested] [flat]
* Replica lag, high read IO, vacuum index scanning bug?
@ 2016-11-02 19:31 Phil Frost <phil@postmates.com>
2016-11-24 19:51 ` Re: Replica lag, high read IO, vacuum index scanning bug? Alvaro Herrera <alvherre@2ndquadrant.com>
0 siblings, 1 reply; 2+ messages in thread
From: Phil Frost @ 2016-11-02 19:31 UTC (permalink / raw)
To: pgsql-admin
We are seeing an issue on RDS 9.4.5 where replica lag gets really high.
This lag seems to be correlated to a saturation of disk read throughput,
and vacuums of one of our larger and more frequently updated tables.
I've heard that there's a bug where the replica will scan indexes
unnecessarily when doing the WAL replay when the vacuums happen. Can
anyone confirm this and maybe point me towards the commit where it was
fixed? Has there been a backport to the 9.4 series?
Any other ideas for investigation or mitigation?
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Replica lag, high read IO, vacuum index scanning bug?
2016-11-02 19:31 Replica lag, high read IO, vacuum index scanning bug? Phil Frost <phil@postmates.com>
@ 2016-11-24 19:51 ` Alvaro Herrera <alvherre@2ndquadrant.com>
0 siblings, 0 replies; 2+ messages in thread
From: Alvaro Herrera @ 2016-11-24 19:51 UTC (permalink / raw)
To: Phil Frost <phil@postmates.com>; +Cc: pgsql-admin
Phil Frost wrote:
> We are seeing an issue on RDS 9.4.5 where replica lag gets really high.
> This lag seems to be correlated to a saturation of disk read throughput,
> and vacuums of one of our larger and more frequently updated tables.
>
> I've heard that there's a bug where the replica will scan indexes
> unnecessarily when doing the WAL replay when the vacuums happen. Can
> anyone confirm this and maybe point me towards the commit where it was
> fixed? Has there been a backport to the 9.4 series?
Hi Phil,
The 9.4 backport of the patch in question is this commit by yours truly:
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=30e3cb307d494990cb38cebff6bfc8b4c...
This will appear in the next minor release of the 9.4 series (as well as
9.5), due out sometime during February 2017.
Thanks,
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2016-11-24 19:51 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2016-11-02 19:31 Replica lag, high read IO, vacuum index scanning bug? Phil Frost <phil@postmates.com>
2016-11-24 19:51 ` Alvaro Herrera <alvherre@2ndquadrant.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox