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

From Michael Paquier
Subject Re: [HACKERS] pg_dump, pg_dumpall and data durability
Date
Msg-id CAB7nPqQDjBDgGgUimqnbV=4JmdF+BybLWxaY5+Den9mrZ-U-0Q@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] pg_dump, pg_dumpall and data durability  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On Wed, Mar 22, 2017 at 7:00 AM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> On Wed, Mar 22, 2017 at 6:24 AM, Andrew Dunstan
> <andrew.dunstan@2ndquadrant.com> wrote:
>> This is really a pretty small patch all things considered, and pretty
>> low-risk (although I haven;t been threough the code in fine detail yet).
>> In the end I'm persuaded by Andres' point that there's actually no
>> practical alternative way to make sure the data is actually synced to disk.
>>
>> If nobody else wants to pick it up I will, unless there is a strong
>> objection.
>
> Thanks!

Thanks Andrew, I can see that this has been committed as 96a7128b.

I also saw that:
https://www.postgresql.org/message-id/75e1b6ff-c3d5-9a26-e38b-3cb22a099ff0@2ndQuadrant.com
I'll send a patch in a bit for the regression tests.
-- 
Michael



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Potential data loss of 2PC files
Next
From: Andrew Dunstan
Date:
Subject: Re: [HACKERS] [PATCH] few fts functions for jsonb