How long replay waits before canceling a conflicting standby query.
At a glance
| Property | Value |
|---|---|
| Parameter | max_standby_streaming_delay |
| Category | Replication |
| Default | 30s |
| Value type | time (ms/s/min) |
| Change scope | Reload (no restart) |
What it does
Maximum delay before recovery cancels a standby query that conflicts with incoming WAL replay. -1 waits indefinitely.
How to apply a change
Takes effect on configuration reload (sighup context). Run SELECT pg_reload_conf(); or send SIGHUP — no restart needed.
Inspect the current value and source with SHOW max_standby_streaming_delay; or SELECT name, setting, unit, context, source FROM pg_settings WHERE name = 'max_standby_streaming_delay';.
Tuning guidance
Raise for read-heavy standbys running long analytical queries (accepting more replication lag), or enable hot_standby_feedback instead to prevent the conflicts at the source.