ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
RocksDB utilizes WriteBatch to ensure atomicity, ensuring that a group of operations is applied as a single unit. While this prevents partial updates, the system relies on the Write-Ahead Log (WAL) for durability and recovery after a crash. A design uncertainty exists regarding the interaction between the WAL and the memtable during recovery. Specifically, i
Goal: ensure that a SQLite database can be returned to a consistent, usable state after a process crashes while a schema‑changing statement (e.g., ALTER TABLE, CREATE INDEX) is being committed. SQLite relies on its rollback journal or Write‑Ahead Log (WAL) to undo partial writes, and the PRAGMA integrity_check procedure can verify B‑tree and index consistenc
On a running PostgreSQL 13 instance, I tried modifying it's wal_level system setting as follows, but it's not being respected: postgres@localhost:postgres> SHOW wal_level +-------------+ | wal_level | |-------------| | replica | +-------------+ SHOW Time: 0.021s postgres@localhost:postgres> ALTER SYSTEM SET wal_level = logical; ALTER SYSTEM Time: 0.007
Write-Ahead Log Recovery Behavior The Prometheus time series database (TSDB) uses a Write-Ahead Log (WAL) to ensure data durability for samples that have not yet been compacted into permanent blocks. In scenarios involving abrupt power loss or unclean shutdowns (such as a SIGKILL), the trailing segment of the WAL can become malformed. Current server behavior
We run Prometheus 2.x and back up TSDB snapshots plus archived WAL segments for disaster recovery. The documented snapshot and WAL replay mechanisms let us restore a point-in-time data directory, but I cannot find any supported way to verify that the restored data actually matches what was in the original instance. The specific uncertainty: after replaying a
Asked · 08 Apr 2022, 06:59 UTC
commented · 13 Apr 2022, 02:11 UTC
sqlite
postgresql
prometheus