Re: XLog changes for 9.3 - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: XLog changes for 9.3
Date
Msg-id 4FD09B5E020000250004818B@gw.wicourts.gov
Whole thread Raw
In response to Re: XLog changes for 9.3  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: XLog changes for 9.3  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> wrote:
> Anything changing filenames will break every HA config anybody has
> anywhere.
It will impact our scripts related to backup and archiving, but I
think we're talking about two or three staff days to cover it in our
shop.
We should definitely make sure that this change is conspicuously
noted.  The scariest part is that there will now be files that
matter with names that previously didn't exist, so lack of action
will cause failure to capture a usable backup.  I don't know that it
merits a bump to 10.0, though.  We test every backup for usability,
as I believe any shop should; failure to cover this should cause
pretty obvious errors pretty quickly if you are testing your
backups.
-Kevin


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: XLog changes for 9.3
Next
From: Tom Lane
Date:
Subject: Re: Avoiding adjacent checkpoint records