On Fri, May 26, 2017 at 4:47 PM, Peter Eisentraut <peter.eisentr...@2ndquadrant.com> wrote: > On 5/26/17 14:16, Michael Paquier wrote: >> So, now that the last round of minor releases has happened and that >> some dust has settled on this patch, shouldn't there be a backpatch? >> If yes, do you need patches for all branches? This problems goes down >> to 9.2 anyway as BASE_BACKUP can generate end-of-backup records. > > Yes, this could be backpatched now. It looks like it will need a bit of > fiddling to get it into all the backbranches. If you want to give it a > closer look, go ahead please.
Attached are patches for 9.2~9.6. There are a couple of conflicts across each version. Particularly in 9.2, I have made the choice to not rename walsender_ready_to_stop to got_SIGINT as this is used as well in basebackup.c to make clearer the code. In 9.3~ the use of this flag is located only within walsender.c. -- Michael
walsender-shutdown-96.patch
Description: Binary data
walsender-shutdown-95.patch
Description: Binary data
walsender-shutdown-93.patch
Description: Binary data
walsender-shutdown-94.patch
Description: Binary data
walsender-shutdown-92.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
