Re: Use durable_unlink for .ready and .done files for WAL segmentremoval - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: Use durable_unlink for .ready and .done files for WAL segmentremoval
Date
Msg-id 20180928183619.GF4184@tamriel.snowman.net
Whole thread Raw
In response to Use durable_unlink for .ready and .done files for WAL segment removal  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Use durable_unlink for .ready and .done files for WAL segmentremoval
List pgsql-hackers
Greetings,

* Michael Paquier (michael@paquier.xyz) wrote:
> While reviewing the archiving code, I have bumped into the fact that
> XLogArchiveCleanup() thinks that it is safe to do only a plain unlink()
> for .ready and .done files when removing a past segment.  I don't think
> that it is a smart move, as on a subsequent crash we may still see
> those, but the related segment would have gone away.  This is not really
> a problem for .done files, but it could confuse the archiver to see some
> .ready files about things that have already gone away.

Is there an issue with making the archiver able to understand that
situation instead of being confused by it..?  Seems like that'd probably
be a good thing to do regardless of this, but that would then remove the
need for this kind of change..

Thanks!

Stephen

Attachment

pgsql-hackers by date:

Previous
From: James Robinson
Date:
Subject: Pithy patch for more detailed error reporting wheneffective_io_concurrency is set to nonzero on platforms lackingposix_fadvise()
Next
From: Andres Freund
Date:
Subject: Odd 9.4, 9.3 buildfarm failure on s390x