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 CAB7nPqR=hUMk4HuHXSG=qO35vOEYue-98GPS_5Mp=REOSJva7A@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] pg_dump, pg_dumpall and data durability  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Responses Re: [HACKERS] pg_dump, pg_dumpall and data durability  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
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!
-- 
Michael



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: [HACKERS] Parallel tuplesort (for parallel B-Tree index creation)
Next
From: David Steele
Date:
Subject: Re: [HACKERS] increasing the default WAL segment size