Incorrect use of errcode_for_file_access in backend code - Mailing list pgsql-hackers

From Michael Paquier
Subject Incorrect use of errcode_for_file_access in backend code
Date
Msg-id 20180902200747.GC1343@paquier.xyz
Whole thread Raw
Responses Re: Incorrect use of errcode_for_file_access in backend code
List pgsql-hackers
Hi all,

While looking at another patch for slot.c, I have noticed what looks
like incorrect use of errcode_for_file_access:
- errcode_for_file_access() is used with rmtree(), which makes no sense
as this comes from common/rmtree.c, and a warning already shows up using
%m.
- ERRCODE_DATA_CORRUPTED is not used to mention corrupted data, and
instead errcode_for_file_access() gets called.

Wouldn't something like the attached provide more adapted error
handling?  That's mostly error handling beautification, so I would be
incline to just fix HEAD.

(I have noticed some inconsistent error string format in autoprewarm.c
on the way.)

Thoughts?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Bug in slot.c and are replication slots ever used at Window?
Next
From: Robert Haas
Date:
Subject: Re: Stored procedures and out parameters