From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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: | 2016-12-06 09:11:27 |
Message-ID: | CAB7nPqQ9DU=SNXqHF5n63nXCDtqAO_kPva+sAKhA6dPfg4ZP_Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Dec 6, 2016 at 6:00 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> One idea is to provide the utility or extension which fsync's the specified
> files and directories (including all the files under them). It may be overkill,
> though. But it would be useful for other purposes, for example, we can
> improve the durability of archived WAL files by setting this utility in
> archive_command, and we can flush any output files generated by psql
> by using it.
That's the pg_copy utility that we talked a couple of months
(year(s)?) back, which would really be useful for archiving, and the
main advantage is that it would be cross-platform. Still the patch
discussed here is more targeted, this makes sure that once pg_dump
leaves, things created are on disk, facilitating the life of users by
not involving an extra step and by making the safe behavior the
default.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2016-12-06 09:57:38 | Re: Quorum commit for multiple synchronous replication. |
Previous Message | Fujii Masao | 2016-12-06 09:00:15 | Re: pg_dump, pg_dumpall and data durability |