Re: Postgres, fsync, and OSs (specifically linux) - Mailing list pgsql-hackers

From Abhijit Menon-Sen
Subject Re: Postgres, fsync, and OSs (specifically linux)
Date
Msg-id 20180519003210.xehe2kfei5nss4mw@toroid.org
Whole thread Raw
In response to Re: Postgres, fsync, and OSs (specifically linux)  (Stephen Frost <sfrost@snowman.net>)
Responses Re: Postgres, fsync, and OSs (specifically linux)  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
At 2018-05-18 20:27:57 -0400, sfrost@snowman.net wrote:
>
> I don't agree with the general notion that we can't have a function
> which handles the complicated bits about the kind of error because
> someone grep'ing the source for PANIC might have to do an additional
> lookup.

Or we could just name the function promote_eio_to_PANIC.

(I understood the objection to be about how 'grep PANIC' wouldn't find
these lines at all, not that there would be an additional lookup.)

-- Abhijit


pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Postgres, fsync, and OSs (specifically linux)
Next
From: Stephen Frost
Date:
Subject: Re: Postgres, fsync, and OSs (specifically linux)