Re: Temporary WAL segments files not cleaned up after an instancecrash - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Temporary WAL segments files not cleaned up after an instancecrash
Date
Msg-id f93fd0a2-6cc2-978f-7a3b-5f34a7d9bc0c@iki.fi
Whole thread Raw
In response to Re: Temporary WAL segments files not cleaned up after an instancecrash  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Temporary WAL segments files not cleaned up after an instancecrash  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On 12/07/18 15:38, Michael Paquier wrote:
> On Thu, Jul 12, 2018 at 01:15:03PM +0300, Heikki Linnakangas wrote:
>> On 12/07/18 10:44, Michael Paquier wrote:
>>> +        snprintf(path, MAXPGPATH, XLOGDIR "/%s", xlde->d_name);
>>> +        elog(DEBUG2, "removed temporary WAL file \"%s\"", path);
>>> +        unlink(path);
>>
>> The elog message says "removed", but the removal actually happens after the
>> elog. "removing" would be more accurate.
> 
> Or just move the elog() after the file is actually removed?  Would you
> be fine with that?

Sure.

- Heikki


pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Temporary WAL segments files not cleaned up after an instancecrash
Next
From: Ashutosh Bapat
Date:
Subject: Re: partition pruning doesn't work with IS NULL clause in multikeyrange partition case