4 ms·
Database plus Copy-On-Write file systems sound like a bad idea. I am imagining a modest 100gb database being re-written for every change. I am sure there is so
by sqeaky 9y ago
Database plus Copy-On-Write file systems sound like a bad idea. I am imagining a modest 100gb database being re-written for every change.
I am sure there is some way to work around this, but wouldn't this be the default behavior with a typical database and typical COW file system?
- X86BSD 9y agoYou might be interested in reading this paper: https://people.freebsd.org/~seanc/postgresql/scale15x-2017-postgresql_zfs_best_practices.pdf https://people.freebsd.org/~seanc/postgresql/scale15x-2017-p...
- sqeaky 9y agoI am interested and I appreciate the thought and link, however these appear to be the slides to a talk without the actual talk. If so they are of limited use because the slides never have all the information the presenter has, and that information is often just a summary. Is this the correct talk: https://youtu.be/dwMQXLOXUco?t=5380 https://youtu.be/dwMQXLOXUco?t=5380 ?
- X86BSD 9y agoYes, sorry about that, that is the corresponding talk to the slides. Thanks for pointing that out.
- cryptonector 9y agoFirst, you have to make sure the page sizes for the FS and DB match. That's a critical requirement. But yes, you'll get write expansion twice.