Re: pg_rewind failure by file deletion in source server

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_rewind failure by file deletion in source server
Date: 2015-08-03 04:01:13
Message-ID: CAB7nPqTAKZyyA_wYvMh-KfLaJk+_JBQFt7wCM-_PEWbYX3jgWg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Aug 2, 2015 at 4:01 AM, Heikki Linnakangas wrote:
> Perhaps it's best if we copy all the WAL files from source in copy-mode, but
> not in libpq mode. Regarding old WAL files in the target, it's probably best
> to always leave them alone. They should do no harm, and as a general
> principle it's best to avoid destroying evidence.
>
> It'd be nice to get some fix for this for alpha2, so I'll commit a fix to do
> that on Monday, unless we come to a different conclusion before that.

+1. Both things sound like a good plan to me.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message 高增琦 2015-08-03 04:03:55 Re: buffer locking fix for lazy_scan_heap
Previous Message Noah Misch 2015-08-03 03:47:40 Re: nodes/*funcs.c inconsistencies