On 04/14/2015 02:24 AM, Tom Lane wrote:
Heikki Linnakangas <[email protected]> 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
--
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
