Re: Replication status in logical replication
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Noah Misch <noah@leadboat.com>
Cc: Masahiko Sawada <sawada.mshk@gmail.com>,
Simon Riggs <simon@2ndquadrant.com>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2017-05-30T17:55:04Z
Lists: pgsql-hackers
On 5/29/17 22:56, Noah Misch wrote: > On Fri, May 19, 2017 at 11:33:48AM +0900, Masahiko Sawada wrote: >> On Wed, Apr 12, 2017 at 5:31 AM, Simon Riggs <simon@2ndquadrant.com> wrote: >>> Looks like a bug that we should fix in PG10, with backpatch to 9.4 (or >>> as far as it goes). >>> >>> Objections to commit? >>> >> >> Seems we still have this issue. Any update or comment on this? Barring >> any objections, I'll add this to the open item so it doesn't get >> missed. > > [Action required within three days. This is a generic notification.] > > The above-described topic is currently a PostgreSQL 10 open item. Peter, > since you committed the patch believed to have created it, you own this open > item. If some other commit is more relevant or if this does not belong as a > v10 open item, please let us know. I would ask Simon to go ahead with this patch if he feels comfortable with it. I'm disclaiming this open item, since it's an existing bug from previous releases (and I have other open items to focus on). -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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