Re: BUG #14806: WAL replay on standby: could not link file "pg_xlog/...4C" to "pg_xlog/...D1": File exists

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: email(at)piotr-stefaniak(dot)me
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14806: WAL replay on standby: could not link file "pg_xlog/...4C" to "pg_xlog/...D1": File exists
Date: 2017-09-08 14:24:45
Message-ID: 19918.1504880685@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

email(at)piotr-stefaniak(dot)me writes:
> We have an archive-only replicating standby. During intensive WAL replay, it
> sometimes happens that the standby will say "58P02: could not link file
> "pg_xlog/[...]" to "pg_xlog/[...]": File exists" as in the example below. It
> looks like some kind of race condition.

This is normal I believe; in any case it looks pretty harmless, since
RemoveXlogFile will just remove the file if it fails to recycle it
as a future xlog segment.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2017-09-08 16:42:44 Re: Old row version in hot chain become visible after a freeze
Previous Message email 2017-09-08 11:58:06 BUG #14806: WAL replay on standby: could not link file "pg_xlog/...4C" to "pg_xlog/...D1": File exists