On 12/30/22 06:59, Nico Kadel-Garcia wrote:
You've apparently not encountered the corruption of a database under heavy load where the cache where swapspace has not yet been propagated to disk. Imagine a server running a lot of virtual machines for an image of what an overly aggressive shutdown timeout can do to your otherwise stable systems.
Wait a moment, if you have memory cached data (dirty pages), the stuff will reach the disk whatever you do to the processes; the kernel will absolutely write any dirty page to disk when unmounting the fs. The problem you are describing can only happen if your database is in a VM, which gets killed during operation. But killing a VM is equivalent to suddenly powering off a bare metal, and if your DB becomes corrupted because of this, it is possibly a low quality software, abusing the "DB" name. Additionally, there are options governing how a "sync" in the VM should be handled (e.g. assure data is in host RAM vs assure data is in host disks). Regards. -- Roberto Ragusa mail at robertoragusa.it _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
