Dan Luu • 3/28/2018

Fsyncgate: errors on fsync are unrecovarable

Read Original

This article archives the 'fsyncgate' email thread where Craig Ringer details a critical PostgreSQL flaw. The issue involves PostgreSQL incorrectly handling fsync() EIO errors, particularly on XFS, by retrying failed syncs. This can lead to completed checkpoints despite unwritten data, resulting in potential data loss. The post argues PostgreSQL should PANIC on fsync failures to ensure data safety.

0 comments
#linux #fsync #postgresql
Fsyncgate: errors on fsync are unrecovarable

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
React vs Browser APIs (Mental Model)
Jivbcoop • 4 votes
2
React, useEffect, and Stale Closures: How to Avoid Them with Dependencies and useRef
Jivbcoop • 3 votes
3
Better react-hook-form Smart Form Components
Maarten Hus • 2 votes
4
Building Type-Safe Compound Components
TkDodo Dominik Dorfmeister • 2 votes
5
Dew Drop – January 15, 2026 (#4583)
Alvin Ashcraft • 1 votes
6
Using Browser Apis In React Practical Guide
Jivbcoop • 1 votes
7
Building a Complete FIRE Calculator App with GitHub Copilot in One Chat Session
James Montemagno • 1 votes