Write-Ahead Logging (WAL)
Cluster focuses on discussions about Write-Ahead Logging (WAL) in databases like PostgreSQL and MySQL, its benefits for write performance, durability, sequential writes, checkpoints, and comparisons to append-only or log-structured storage.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Isn't this just an issue if there are too much writes?And doesn't a WAL help with that?
Won't it just... write more WAL files?
Because it has to copy and write entire pages instead of only force a flush of log records due to a WAL?
Isn't that why a WAL exists, so you didn't actually need to do that with eg postgres and other rdbms?
Nah, PostgreSQL is sticky, it has a Write Ahead Log !!
This takes advantage of log-structured storage so there isn't any "undoing".
this is exactly what I meant - WAL is your friend.
couldn't you just store your data in append-only fashion?
You don't have to stop to copy from a log-structured file
Write-ahead logs seem to be rediscovered every 3-5 years.