Whether to retry after an fsync failure instead of panicking.
At a glance
| Property | Value |
|---|---|
| Parameter | data_sync_retry |
| Category | Error Handling |
| Default | off |
| Value type | boolean / enum / numeric |
| Change scope | Restart required |
What it does
When off (default), an fsync failure causes a PANIC, because on Linux a failed fsync may have discarded dirty data and retrying is unsafe.
How to apply a change
Requires a full server restart (postmaster context). Set it in postgresql.conf and restart PostgreSQL.
Inspect the current value and source with SHOW data_sync_retry; or SELECT name, setting, unit, context, source FROM pg_settings WHERE name = 'data_sync_retry';.
Tuning guidance
Leave off on Linux. Only set on if your kernel/storage is known to preserve dirty data across fsync errors — almost never.