Re: pgsql: Fix failure to check for open() or fsync() failures. - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pgsql: Fix failure to check for open() or fsync() failures.
Date
Msg-id 32282.1545874522@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Fix failure to check for open() or fsync() failures.  (Michael Paquier <michael@paquier.xyz>)
Responses Re: pgsql: Fix failure to check for open() or fsync() failures.  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes:
> On Wed, Dec 26, 2018 at 05:55:36PM -0500, Tom Lane wrote:
>> It appears to me that the code is intentionally not worrying about
>> fsync failure, so it seems wrong for it to FATAL out if it's unable
>> to open the file to fsync it.  And it surely shouldn't do so if the
>> file isn't there.

> My point is a bit different though: it seems to me that we could just
> call BasicOpenFilePerm() and remove the stat() to do exactly the same
> things, simplifying the code.

Oh, I see.  Yeah, if we're ignoring errors anyway, the stat calls
seem redundant.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: random() (was Re: New GUC to sample log queries)
Next
From: Tom Lane
Date:
Subject: Re: random() (was Re: New GUC to sample log queries)