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

From Mark Kirkwood
Subject Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS
Date
Msg-id f026ab0b-c627-6e93-5be6-83ba858d43e3@catalyst.net.nz
Whole thread Raw
In response to Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS
List 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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pruning disabled for array, enum, record, range type partition keys
Next
From: Peter Geoghegan
Date:
Subject: Adding an LWLockHeldByMe()-like function that reports if any buffercontent lock is held