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

On 04/08/2018 05:27 AM, Craig Ringer wrote:> More below, but here's an 
idea #5: decide InnoDB has the right idea, and
> go to using a single massive blob file, or a few giant blobs.

FYI: MySQL has by default one file per table these days. The old 
approach with one massive file was a maintenance headache so they change 
the default some releases ago.

https://dev.mysql.com/doc/refman/8.0/en/innodb-multiple-tablespaces.html

Andreas