Re: XLog changes for 9.3

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Simon Riggs" <simon(at)2ndQuadrant(dot)com>, "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: XLog changes for 9.3
Date: 2012-06-07 17:15:26
Message-ID: 4FD09B5E020000250004818B@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs <simon(at)2ndQuadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-06-07 17:20:33 Re: Avoiding adjacent checkpoint records
Previous Message Andres Freund 2012-06-07 17:12:06 Re: XLog changes for 9.3