Postgres Pro
Downloads
Home   >   mailing lists

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

From Michael Paquier
Subject Re: pgsql: Fix failure to check for open() or fsync() failures.
Date
Msg-id 20181227021039.GI2106@paquier.xyz
Whole thread Raw
In response to Re: pgsql: Fix failure to check for open() or fsync() failures.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql: Fix failure to check for open() or fsync() failures.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On Wed, Dec 26, 2018 at 08:35:22PM -0500, Tom Lane wrote:
> Oh, I see.  Yeah, if we're ignoring errors anyway, the stat calls
> seem redundant.

For this one, I think that we could simplify as attached (this causes
open() to fail additionally because of the sync flags, but that's not
really worth worrying).  Thoughts?
--
Michael
Attachment

pgsql-hackers by date:

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