Skip to main content
Write-ahead logging

Write-ahead logging

Search complete. 2 mentions across 1 episode found for "Write-ahead logging".

Sep 20, 2026

speaker_0HOST
19:43
And PostgreSQL can actually handle the relentless active message queue polling.
speaker_1HOST
19:46
Without breaking a sweat, PostgreSQL provides ACID guarantees and utilizes write-ahead logging, or WAL.
speaker_1HOST
19:53
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.
speaker_0HOST
20:02
Because of the write-ahead log.
speaker_1HOST
20:03
Right.
speaker_1HOST
20:03
The WAL replays the incomplete transactions, and your pipeline graphs aren't corrupted.
speaker_1HOST
20:07
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.
speaker_0HOST
20:18
So standalone with Postgresible gives you enterprise durability without the microservice memory task.

We value your privacy

We use cookies to understand how you use our platform and to improve your experience. Click “Accept All” to consent, or “Decline non-essential” to opt out of non-essential cookies. Read our Privacy Policy.