| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, David Steele <david(at)pgmasters(dot)net>, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump, pg_dumpall and data durability |
| Date: | 2017-03-21 22:00:23 |
| Message-ID: | CAB7nPqR=hUMk4HuHXSG=qO35vOEYue-98GPS_5Mp=REOSJva7A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 22, 2017 at 6:24 AM, Andrew Dunstan
<andrew(dot)dunstan(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2017-03-21 22:02:44 | Re: increasing the default WAL segment size |
| Previous Message | Thomas Munro | 2017-03-21 21:49:28 | Re: Parallel tuplesort (for parallel B-Tree index creation) |