Re: [HACKERS] Replication status in logical replication
Michael Paquier <michael.paquier@gmail.com>
From: Michael Paquier <michael.paquier@gmail.com>
To: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: Simon Riggs <simon@2ndquadrant.com>, Petr Jelinek <petr.jelinek@2ndquadrant.com>, Thomas Munro <thomas.munro@enterprisedb.com>, Vaishnavi Prabakaran <vaishnaviprabakaran@gmail.com>, Daniel Gustafsson <daniel@yesql.se>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Noah Misch <noah@leadboat.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2018-01-16T06:21:41Z
Lists: pgsql-hackers
On Tue, Jan 16, 2018 at 10:40:43AM +0900, Masahiko Sawada wrote: > On Sun, Jan 14, 2018 at 12:43 AM, Simon Riggs <simon@2ndquadrant.com> wrote: >> On 9 January 2018 at 04:36, Masahiko Sawada <sawada.mshk@gmail.com> wrote: >> We're not talking about standbys, so the message is incorrect. > > Ah, I understood. How about "\"%s\" has now caught up with upstream > server"? +1. -- Michael
Commits
-
Make logical WAL sender report streaming state appropriately
- 98e2c298c2f5 9.4.19 landed
- 19648375cc30 9.5.14 landed
- d5eb1fe0dc71 9.6.10 landed
- 11abea37d5d1 10.5 landed
- 0414ac6a1eb2 11.0 landed
- 9a7b7adc130a 12.0 landed