Re: Two pg_rewind patches (auto generate recovery conf and ensure clean shutdown)

Thomas Munro <thomas.munro@gmail.com>

From: Thomas Munro <thomas.munro@gmail.com>

To: Paul Guo <pguo@pivotal.io>

Cc: Michael Paquier <michael@paquier.xyz>, pgsql-hackers <pgsql-hackers@postgresql.org>, Jimmy Yih <jyih@pivotal.io>, Ashwin Agrawal <aagrawal@pivotal.io>

Date: 2019-07-01T11:34:34Z

Lists: pgsql-hackers

On Fri, Apr 19, 2019 at 3:41 PM Paul Guo <pguo@pivotal.io> wrote:
> I updated the patches as attached following previous discussions.

Hi Paul,

Could we please have a fresh rebase now that the CF is here?

Thanks,

-- 
Thomas Munro
https://enterprisedb.com

Commits

Improve test coverage of pg_rewind
- 55ba56415bae 13.0 landed
Improve handling and coverage of --no-ensure-shutdown in pg_rewind
- caa078353ecd 13.0 landed
Fix issues in pg_rewind with --no-ensure-shutdown/--write-recovery-conf
- 6837632b758e 13.0 landed
Fix --dry-run mode of pg_rewind
- c2e3b311d9ef 12.1 landed
- 6f3823b03560 13.0 landed
pg_rewind: test new --write-recovery-conf functionality
- 7524c788743f 13.0 landed
pg_rewind: Allow writing recovery configuration
- 927474ce1a24 13.0 landed
Have pg_rewind run crash recovery before rewinding
- 5adafaf176d0 13.0 landed
Split out recovery confing-writing code from pg_basebackup
- caba97a9d9f4 13.0 landed
Switch TAP tests of pg_rewind to use non-superuser role, take two
- d9f543e9e9be 12.0 cited