| Type: | bool |
| Default: | off |
| Context: | sighup |
| Restart: | false |
Specifies whether or not a hot standby will send feedback to the primary or upstream standby about queries currently executing on the standby. This parameter can be used to eliminate query cancels caused by cleanup records, but can cause database bloat on the primary for some workloads. Feedback messages will not be sent more frequently than once per wal_receiver_status_interval. The default value is off. This parameter can only be set in the postgresql.conf file or on the server command line.
If cascaded replication is in use the feedback is passed upstream until it eventually reaches the primary. Standbys make no other use of feedback they receive other than to pass upstream.
Recommendations
Helps avoid query cancel on the replicas in most cases. Turn it off for a replica which does long-running reports and is allowed to lag.
On StackOverflow
On pgsql-hackers
- RE: Conflict Detection and Resolution
- Re: Disallow altering invalidated replication slots
- doc: Mention clock synchronization recommendation for hot_standby_feedback
- Re: doc: Mention clock synchronization recommendation for hot_standby_feedback
- RE: Conflict detection for update_deleted in logical replication