Re: [HACKERS] some pg_rewind usability issues

2015-09-17 Thread Michael Paquier
On Wed, Sep 16, 2015 at 9:46 PM, Michael Paquier wrote: > That's something that we discussed in this CF's patch to ease the > handling of timeline switches when rewinding a node, I wouldn't have > any objection to get that backpatched to 9.5 though (the > DB_SHUTDOWNED_IN_RECOVERY part I mean).

Re: [HACKERS] some pg_rewind usability issues

2015-09-16 Thread Robert Haas
On Wed, Sep 16, 2015 at 10:28 PM, Peter Eisentraut wrote: > pg_rewind --source-server uses the libpq default mechanisms for the > database, but that's useless for pg_rewind, which can just always use > dbname=postgres, like other database-agnostic utilities. Keep in mind that

Re: [HACKERS] some pg_rewind usability issues

2015-09-16 Thread Michael Paquier
On Wed, Sep 16, 2015 at 7:28 PM, Peter Eisentraut wrote: > pg_rewind requires that the target server be shut down cleanly, but does > not accept shutdown in recovery. Is that necessary? > [blah] > If I patch pg_rewind to allow shutdown in recovery, it goes slightly > easier, but

[HACKERS] some pg_rewind usability issues

2015-09-16 Thread Peter Eisentraut
pg_rewind --source-server uses the libpq default mechanisms for the database, but that's useless for pg_rewind, which can just always use dbname=postgres, like other database-agnostic utilities. pg_rewind requires that the target server be shut down cleanly, but does not accept shutdown in