On Sun, Jul 9, 2017 at 8:00 PM, Stephen Frost <sfr...@snowman.net> wrote: > * Noah Misch (n...@leadboat.com) wrote: >> [Action required within three days. This is a generic notification.] >> >> The above-described topic is currently a PostgreSQL 10 open item. Stephen, >> 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. Otherwise, please observe the policy on >> open item ownership and send a status update within three calendar days of >> this message. Include a date for your subsequent status update. Testers may >> discover new open items at any time, and I want to plan to get them all fixed >> well in advance of shipping v10. Consequently, I will appreciate your >> efforts >> toward speedy resolution. Thanks. > > I'm out of town this week but will review the patch from Masahiko and > provide a status update by July 17th.
Good to know. I was planning to review the patch within 24 hours. I have spotted at least one bug in the patch: there is no need to wait for the backup history file and the last segment to be archived on a standby unless archive_mode = always, meaning that XLogArchivingAlways() needs to be used instead of XLogArchivingActive(). There may be other things, but I am lacking time and brain power now for a complete analysis. -- Michael -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers