| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | David Steele <david(at)pgmasters(dot)net> |
| Cc: | Christophe Pettus <xof(at)thebuild(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Remove Deprecated Exclusive Backup Mode |
| Date: | 2019-02-25 21:15:53 |
| Message-ID: | 20190225211553.qj6om7prjgzybiaq@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2019-02-25 20:43:01 +0200, David Steele wrote:
> fsync() is the major corruption issue we are facing right now but that
> doesn't mean there aren't other sources of corruption we should be thinking
> about. I've thought about this one a lot and it scares me.
FWIW, I think this kind of issue practially bites a *LOT* more people
than the fsync() issue.
> I've worked on ways to make it better, but all of them break something and
> involve compromises that are nearly as severe as removing exclusive backups
> entirely.
There've been plenty proposals to make non-exclusive backups less
painful in this thread, so ...?
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christophe Pettus | 2019-02-25 21:20:21 | Re: Remove Deprecated Exclusive Backup Mode |
| Previous Message | Andres Freund | 2019-02-25 21:14:17 | Re: Remove Deprecated Exclusive Backup Mode |