| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: pg_basebackup, pg_receivexlog and data durability (was: silent data loss with ext4 / all current versions) |
| Date: | 2016-09-03 13:23:26 |
| Message-ID: | CAB7nPqSmXKjj+dxKjHWn-wJvDrCVJ2rTTQbxuQ0weRhYuSZuww@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Sep 3, 2016 at 10:22 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> On Sat, Sep 3, 2016 at 10:21 PM, Michael Paquier
> <michael(dot)paquier(at)gmail(dot)com> wrote:
>> Oh, well. I have just implemented it on top of the two other patches
>> for pg_basebackup. For pg_receivexlog, I am wondering if it makes
>> sense to have it. That would be trivial to implement it, and I think
>> that we had better make the combination of --synchronous and --nosync
>> just leave with an error. Thoughts about having that for
>> pg_receivexlog?
>
> With patches that's actually better..
Meh, meh et meh.
--
Michael
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Relocation-fsync-routines-of-initdb-into-src-common.patch | application/x-patch | 19.6 KB |
| 0002-Issue-fsync-more-carefully-in-pg_receivexlog-and-pg_.patch | application/x-patch | 10.4 KB |
| 0003-Add-nosync-option-to-pg_basebackup.patch | application/x-patch | 8.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-09-03 13:26:21 | Re: Speedup twophase transactions |
| Previous Message | Michael Paquier | 2016-09-03 13:22:39 | Re: pg_basebackup, pg_receivexlog and data durability (was: silent data loss with ext4 / all current versions) |