From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: XLog changes for 9.3 |
Date: | 2012-06-07 17:42:30 |
Message-ID: | CA+TgmoYWGrrt7d=vXhbp1rbf22bmm-FjrSPSPD1EnYnW0pevog@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jun 7, 2012 at 1:40 PM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
>> But if you're just using regexp matching against pathnames, your
>> tool will be just fine. Do your tools actually rely on the
>> occasional absence of a file in what would otherwise be the usual
>> sequence of files?
>
> To save "snapshot" backups for the long term, we generate a list of
> the specific WAL files needed to reach a consistent recovery point
> from a given base backup. We keep monthly snapshot backups for a
> year. We currently determine the first and last file needed, and
> then create a list of all the WAL files to save. We error out if
> any are missing, so we do skip the FF file.
OK, I see. Still, I think there are a lot of people who don't do
anything that complex, and won't be affected. But I agree we had
better clearly release-note it as an incompatibility.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Ants Aasma | 2012-06-07 17:56:17 | Re: 9.2beta1, parallel queries, ReleasePredicateLocks, CheckForSerializableConflictIn in the oprofile |
Previous Message | Lonni J Friedman | 2012-06-07 17:41:36 | pg_basebackup blocking all queries with horrible performance |