Skip site navigation (1) Skip section navigation (2)

Re: pg_basebackup, pg_receivexlog and data durability (was: silent data loss with ext4 / all current versions)

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: pg_basebackup, pg_receivexlog and data durability (was: silent data loss with ext4 / all current versions)
Date: 2016-09-03 13:23:26
Message-ID: CAB7nPqSmXKjj+dxKjHWn-wJvDrCVJ2rTTQbxuQ0weRhYuSZuww@mail.gmail.com (view raw, whole thread or download thread mbox)
Thread:
Lists: pgsql-hackers
On Sat, Sep 3, 2016 at 10:22 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> On Sat, Sep 3, 2016 at 10:21 PM, Michael Paquier
> <michael(dot)paquier(at)gmail(dot)com> wrote:
>> Oh, well. I have just implemented it on top of the two other patches
>> for pg_basebackup. For pg_receivexlog, I am wondering if it makes
>> sense to have it. That would be trivial to implement it, and I think
>> that we had better make the combination of --synchronous and --nosync
>> just leave with an error. Thoughts about having that for
>> pg_receivexlog?
>
> With patches that's actually better..

Meh, meh et meh.
-- 
Michael

Attachment: 0001-Relocation-fsync-routines-of-initdb-into-src-common.patch
Description: application/x-patch (19.6 KB)
Attachment: 0002-Issue-fsync-more-carefully-in-pg_receivexlog-and-pg_.patch
Description: application/x-patch (10.4 KB)
Attachment: 0003-Add-nosync-option-to-pg_basebackup.patch
Description: application/x-patch (8.3 KB)

In response to

Responses

pgsql-hackers by date

Next:From: Michael PaquierDate: 2016-09-03 13:26:21
Subject: Re: Speedup twophase transactions
Previous:From: Michael PaquierDate: 2016-09-03 13:22:39
Subject: Re: pg_basebackup, pg_receivexlog and data durability (was: silent data loss with ext4 / all current versions)

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group