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

Re: silent data loss with ext4 / all current versions

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, dpage(at)pgadmin(dot)org, Guillaume Lelarge <guillaume(dot)lelarge(at)dalibo(dot)com>
Subject: Re: silent data loss with ext4 / all current versions
Date: 2016-03-18 06:08:32
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Fri, Mar 18, 2016 at 12:03 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> This is a *much* more expensive approach though. Doing the fsync
> directly after modifying the file. One file by one file. Will usually
> result in each fsync blocking for a while.
> In comparison of doing a flush and then an fsync pass over the whole
> directory will usually only block seldomly. The flushes for all files
> can be combined into very few barrier operations.

Hm... OK. I'd really like to keep the run of pg_rewind minimal as well
if possible. So here you go.

Attachment: 0001-Close-file-descriptor-associated-to-backup_label-cor.patch
Description: binary/octet-stream (924 bytes)
Attachment: 0002-fsync-properly-files-modified-by-pg_rewind.patch
Description: binary/octet-stream (3.6 KB)
Attachment: 0003-Avoid-potential-data-loss-in-pg_receivexlog.patch
Description: binary/octet-stream (4.6 KB)

In response to


pgsql-hackers by date

Next:From: Michael PaquierDate: 2016-03-18 06:13:15
Subject: Re: insufficient qualification of some objects in dump files
Previous:From: Thomas MunroDate: 2016-03-18 05:30:35
Subject: Re: Proposal: BSD Authentication support

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