Hi,

The <https://www.postgresql.org/docs/13/wal-intro.html> document states, that in case of ext3 filesystems, filesystem journaling can be configured with data=writeback option to increase performance (in specific cases).

Per my understanding this causes some of the filesystem integrity mechanism to be loosened and in case of PostgreSQL data partition it would be okay because WAL files replicate this functionality at a higher level.

What about the storage of WAL files itself? Wouldn't it be possible that in case of unexpected reboot and dirty file system these files get corrupted, making the database state impossible to bring to operational level?


--
Lukasz Biegaj | Unity Group | https://www.unitygroup.com/
System Architect, AWS Solutions Architect


Reply via email to