Postgres Pro
Downloads
Home   >   mailing lists

Re: [BUGS] BUG #14806: WAL replay on standby: could not link file "pg_xlog/...4C" to "pg_xlog/...D1": File exists - Mailing list pgsql-bugs

From Tom Lane
Subject Re: [BUGS] BUG #14806: WAL replay on standby: could not link file "pg_xlog/...4C" to "pg_xlog/...D1": File exists
Date
Msg-id 19918.1504880685@sss.pgh.pa.us
Whole thread Raw
In response to [BUGS] BUG #14806: WAL replay on standby: could not link file"pg_xlog/...4C" to "pg_xlog/...D1": File exists  (email@piotr-stefaniak.me)
List pgsql-bugs
Tree view 
email@piotr-stefaniak.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


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: email@piotr-stefaniak.me
Date:
Subject: [BUGS] BUG #14806: WAL replay on standby: could not link file"pg_xlog/...4C" to "pg_xlog/...D1": File exists
Next
From: Alvaro Herrera
Date:
Subject: Re: [BUGS] Old row version in hot chain become visible after a freeze