| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net>, Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: backup tools ought to ensure created backups are durable |
| Date: | 2016-03-29 06:46:34 |
| Message-ID: | 56FA24CA.8060609@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/28/16 11:03 AM, Magnus Hagander wrote:
>
> That should work yeah. And given that we already use that check in other
> places, it seems it should be perfectly safe. And as long as we only do
> a WARNING and not abort if the fsync fails, we should be OK if people
> intentionally store their backups on an fs that doesn't speak fsync (if
> that exists), in which case I don't really think we even need a switch
> to turn it off.
I'd even go so far as spitting out a warning any time we can't fsync
(maybe that's what you're suggesting?)
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2016-03-29 06:57:17 | Re: Alter or rename enum value |
| Previous Message | Kyotaro HORIGUCHI | 2016-03-29 06:43:07 | Re: IF (NOT) EXISTS in psql-completion |