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

From Craig Ringer
Subject Re: Postgres, fsync, and OSs (specifically linux)
Date
Msg-id CAMsr+YGsvYmJ0aRuV7zNf-rmi53bzFF8yrsgrNBm9yOY8FYD0g@mail.gmail.com
Whole thread Raw
In response to Re: Postgres, fsync, and OSs (specifically linux)  (Andres Freund <andres@anarazel.de>)
Responses Re: Postgres, fsync, and OSs (specifically linux)  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On 1 May 2018 at 00:09, Andres Freund <andres@anarazel.de> wrote:

> It's not. Only SYNC_FILE_RANGE_WAIT_{BEFORE,AFTER} eat errors. Which
> seems sensible, because they could be considered data integrity
> operations.

Ah, I misread that. Thankyou.

>> I'm very suspicious about the safety of the msync() path too.
>
> That seems justified however:

I'll add EIO tests there.

-- 
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: Юрий Соколов
Date:
Subject: Re: [HACKERS] Clock with Adaptive Replacement
Next
From: Amit Langote
Date:
Subject: Re: FOR EACH ROW triggers on partitioned tables