Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS

From: Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Greg Stark <stark(at)mit(dot)edu>, Andres Freund <andres(at)anarazel(dot)de>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Anthony Iliopoulos <ailiop(at)altatus(dot)com>, Geoff Winkless <pgsqladmin(at)geoff(dot)dj>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Robert Haas <robertmhaas(at)gmail(dot)com>, 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-18 23:31:50
Message-ID: f026ab0b-c627-6e93-5be6-83ba858d43e3@catalyst.net.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 19/04/18 00:45, Craig Ringer wrote:

>
> I guarantee you that when you create a 100GB EBS volume on AWS EC2,
> you don't get 100GB of storage preallocated. AWS are probably pretty
> good about not running out of backing store, though.
>
>

Some db folks (used to anyway) advise dd'ing to your freshly attached
devices on AWS (for performance mainly IIRC), but that would help
prevent some failure scenarios for any thin provisioned storage (but
probably really annoy the admins' thereof).

regards
Mark

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2018-04-18 23:53:29 Adding an LWLockHeldByMe()-like function that reports if any buffer content lock is held
Previous Message Tom Lane 2018-04-18 22:56:31 Re: pruning disabled for array, enum, record, range type partition keys