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

From Bossart, Nathan
Subject Re: Use durable_unlink for .ready and .done files for WAL segmentremoval
Date
Msg-id 6AD08B49-6894-4A8E-9FEA-42A0FA864BED@amazon.com
Whole thread Raw
In response to Re: Use durable_unlink for .ready and .done files for WAL segmentremoval  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Use durable_unlink for .ready and .done files for WAL segmentremoval  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On 11/27/18, 3:53 PM, "Michael Paquier" <michael@paquier.xyz> wrote:
> On Tue, Nov 27, 2018 at 09:49:29PM +0000, Bossart, Nathan wrote:
>> That sounds good to me.  I was actually thinking of using the same
>> retry counter that we use for pgarch_archiveXlog(), but on second
>> thought, it is probably better to have two independent retry counters
>> for these two unrelated operations.
>
> What I had in mind was two different variables if what I wrote was
> unclear, possibly with the same value, as archiving failure and failure
> with orphan file removals are two different concepts.

+1

Nathan


pgsql-hackers by date:

Previous
From: Nikhil Sontakke
Date:
Subject: Re: [HACKERS] logical decoding of two-phase transactions
Next
From: Dmitry Dolgov
Date:
Subject: Re: Global snapshots