| From: | Andreas Karlsson <andreas(at)proxel(dot)se> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Bruce Momjian <bruce(at)momjian(dot)us>, 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-08 09:41:06 |
| Message-ID: | bc2835f3-5c30-e799-9fdd-bfbfa520c433@proxel.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2018-04-08 10:30:31 | Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS |
| Previous Message | Thomas Munro | 2018-04-08 09:17:52 | Re: Checkpoint not retrying failed fsync? |