Re: [HACKERS] Replication status in logical replication - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: [HACKERS] Replication status in logical replication
Date
Msg-id CANP8+jKRrC_0xmc9ndqwmW+L-iNtoHG53EbujkdWWTmmnb6TRA@mail.gmail.com
Whole thread Raw
In response to [HACKERS] Replication status in logical replication  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: [HACKERS] Replication status in logical replication  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
On 22 March 2017 at 02:50, Masahiko Sawada <sawada.mshk@gmail.com> wrote:

> When using logical replication, I ran into a situation where the
> pg_stat_replication.state is not updated until any wal record is sent
> after started up. For example, I set up logical replication with 2
> subscriber and restart the publisher server, but I see the following
> status for a while (maybe until autovacuum run).
...

> Attached patch fixes this behavior by updating WalSndCaughtUp before
> trying to read next WAL if already caught up.

Looks like a bug that we should fix in PG10, with backpatch to 9.4 (or
as far as it goes).

Objections to commit?

-- 
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Dmitry Ivanov
Date:
Subject: Re: [HACKERS] Possible problem in Custom Scan API
Next
From: Claudio Freire
Date:
Subject: Re: [HACKERS] Vacuum: allow usage of more than 1GB of work mem