All Your GUCs in a Row: hot_standby

The hot_standby PostgreSQL parameter controls whether a standby server accepts read-only queries during WAL replay. Defaulting to on since PostgreSQL 10, it requires the primary's wal_level to be replica or higher and has no effect on the primary itself. The real tuning work lies in max_standby_streaming_delay, max_standby_archive_delay, and hot_standby_feedback, which manage the conflict between WAL replay speed and query availability. Turning it off is only justified for dedicated failover standbys where zero query conflicts and minimal lag are the priority.

Source: https://postgr.es/p/9qQ. 8sync News only summarizes and links out; content copyright belongs to the authors and original sources.