On Wed, Jun 17, 2015 at 9:07 PM, Fujii Masao wrote:
> On Wed, Jun 17, 2015 at 4:57 PM, Vladimir Borodin wrote:
>>
>> 17 июня 2015 г., в 9:48, Michael Paquier
>> написал(а):
>>
>> On Wed, Jun 17, 2015 at 3:17 PM, Michael Paquier
>> wrote:
>>
>> As pointed by dev1ant on the original bug report, p
On Wed, Jun 17, 2015 at 4:57 PM, Vladimir Borodin wrote:
>
> 17 июня 2015 г., в 9:48, Michael Paquier
> написал(а):
>
> On Wed, Jun 17, 2015 at 3:17 PM, Michael Paquier
> wrote:
>
> As pointed by dev1ant on the original bug report, process_remote_file
> should ignore files named as pg_xlog/xlogt
> 17 июня 2015 г., в 9:48, Michael Paquier
> написал(а):
>
> On Wed, Jun 17, 2015 at 3:17 PM, Michael Paquier
> wrote:
>> As pointed by dev1ant on the original bug report, process_remote_file
>> should ignore files named as pg_xlog/xlogtemp.*, and I think that this
>> is the right thing to do.
On Wed, Jun 17, 2015 at 3:17 PM, Michael Paquier
wrote:
> As pointed by dev1ant on the original bug report, process_remote_file
> should ignore files named as pg_xlog/xlogtemp.*, and I think that this
> is the right thing to do. Any objections for a patch that at the same
> time makes "xlogtemp."
Hi all,
I just bumped into this report regarding pg_rewind, that impacts as
well the version shipped in src/bin/pg_rewind:
https://github.com/vmware/pg_rewind/issues/45
In short, the issue refers to the fact that if the source server
filemap includes xlogtemp files pg_rewind will surely fail with
