Re: pg_dump, pg_dumpall and data durability - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pg_dump, pg_dumpall and data durability
Date
Msg-id CA+TgmoY_Nk1jL0r_LPukFQS7WdJTe859F68w7oH3j+R60r=e3A@mail.gmail.com
Whole thread Raw
In response to Re: pg_dump, pg_dumpall and data durability  (Andres Freund <andres@anarazel.de>)
Responses Re: pg_dump, pg_dumpall and data durability  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
On Sun, Nov 13, 2016 at 4:18 AM, Andres Freund <andres@anarazel.de> wrote:
> On 2016-11-08 18:18:01 -0500, Tom Lane wrote:
>> I think this might be better addressed by adding something to backup.sgml
>> pointing out that you'd better fsync or sync your backups before assuming
>> that they can't be lost.
>
> How does a normal user do that? I don't think there's a cross-platform
> advice we can give, and even on *nix the answer basically is 'sync;
> sync;' which is a pretty big hammer, and might be completely
> unacceptable on a busy server.

Yeah, that's a pretty fair point.  I see the point of this patch
pretty clearly but somehow it makes me nervous anyway.  I'm not sure
there's any better alternative to what's being proposed, though.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: proposal: psql \setfileref
Next
From: Tom Lane
Date:
Subject: Re: Snapshot too old logging