Re: pgsql: Don't archive bogus recycled or preallocated files after timelin - Mailing list pgsql-committers

From Heikki Linnakangas
Subject Re: pgsql: Don't archive bogus recycled or preallocated files after timelin
Date
Msg-id 552CB5E4.8050207@iki.fi
Whole thread Raw
In response to Re: pgsql: Don't archive bogus recycled or preallocated files after timelin  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql: Don't archive bogus recycled or preallocated files after timelin  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
On 04/14/2015 02:24 AM, Tom Lane wrote:
> Heikki Linnakangas <heikki.linnakangas@iki.fi> writes:
>> To fix, whenever we switch to a new timeline, scan the data directory for
>> WAL segments on the old timeline, but with a higher segment number, and
>> remove them.
>
> Wait a minute.  Didn't you just break PITR scenarios?  The *entire point*
> of the multiple-timeline mechanism is that you can start a new WAL history
> from a point in the past without destroying WAL history after that point
> on the old timeline.

It deletes the files belonging to other timelines from pg_xlog only. The
WAL archive is not touched.

- Heikki



pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Don't archive bogus recycled or preallocated files after timelin
Next
From: Heikki Linnakangas
Date:
Subject: pgsql: Reorganize our CRC source files again.