Re: pgsql: Don't archive bogus recycled or preallocated files after timelin

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: hlinnaka(at)iki(dot)fi
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Don't archive bogus recycled or preallocated files after timelin
Date: 2015-04-14 14:32:06
Message-ID: 2843.1429021926@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Heikki Linnakangas <hlinnaka(at)iki(dot)fi> writes:
> On 04/14/2015 02:24 AM, Tom Lane wrote:
>> 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.

How do we know those files are in the WAL archive?

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Heikki Linnakangas 2015-04-14 14:49:21 Re: pgsql: Don't archive bogus recycled or preallocated files after timelin
Previous Message Heikki Linnakangas 2015-04-14 14:09:28 pgsql: Use Intel SSE 4.2 CRC instructions where available.