| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Replication status in logical replication |
| Date: | 2017-04-11 20:31:42 |
| Message-ID: | CANP8+jKRrC_0xmc9ndqwmW+L-iNtoHG53EbujkdWWTmmnb6TRA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 22 March 2017 at 02:50, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Claudio Freire | 2017-04-11 20:38:51 | Re: Vacuum: allow usage of more than 1GB of work mem |
| Previous Message | Dmitry Ivanov | 2017-04-11 20:28:17 | Re: Possible problem in Custom Scan API |