
Write-ahead logging
2
MENTIONS
1
EPISODES
1
PODCASTS
Search complete. 2 mentions across 1 episode found for "Write-ahead logging".
Sep 20, 2026
Kestra 2.0 Self-Hosting Strategy and Architecture
S
19:43speaker_0HOST
And PostgreSQL can actually handle the relentless active message queue polling.
S
19:46speaker_1HOST
Without breaking a sweat, PostgreSQL provides ACID guarantees and utilizes write-ahead logging, or WAL.
S
19:53speaker_1HOST
Because Kestra stores all execution state in the repository database, PostgreSQL ensures that if your power cuts out abruptly, the database recovers cleanly on the next boot.
S
20:02speaker_0HOST
Because of the write-ahead log.
S
20:03speaker_1HOST
Right.
S
20:03speaker_1HOST
The WAL replays the incomplete transactions, and your pipeline graphs aren't corrupted.
S
20:07speaker_1HOST
It fits perfectly within that 4GB RAM envelope we talked about, leaving about 1.5GB to 2GB of free dynamic headroom on the host for when tasks actually need to process data.
S
20:18speaker_0HOST
So standalone with Postgresible gives you enterprise durability without the microservice memory task.