| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Anthony Iliopoulos <ailiop(at)altatus(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Catalin Iacob <iacobcatalin(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS |
| Date: | 2018-04-04 14:42:18 |
| Message-ID: | CAMsr+YFFYO1eHTGzT1wnoRW6L_PmP8MDFhbcdVBjBKQSF9fkYw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4 April 2018 at 22:25, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> On Wed, Apr 4, 2018 at 10:09:09PM +0800, Craig Ringer wrote:
> > On 4 April 2018 at 22:00, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> >
> >
> > It's the error reporting issues around closing and reopening files
> with
> > outstanding buffered I/O that's really going to hurt us here. I'll be
> > expanding my test case to cover that shortly.
> >
> >
> >
> > Also, just to be clear, this is not in any way confined to xfs and/or
> lvm as I
> > originally thought it might be.
> >
> > Nor is ext3/ext4's errors=remount-ro protective. data_err=abort doesn't
> help
> > either (so what does it do?).
>
> Anthony Iliopoulos reported in this thread that errors=remount-ro is
> only affected by metadata writes.
Yep, I gathered. I was referring to data_err.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksandr Parfenov | 2018-04-04 14:49:08 | Re: new function for tsquery creartion |
| Previous Message | Dmitry Ivanov | 2018-04-04 14:33:47 | Re: new function for tsquery creartion |