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.
- Are there any performance effects on master when using postgres streaming replication with hot_standby_feedback on
- How can I fix PostgreSQL canceling statement error on Google SQL?
- Manage conflicts and lag on Postgres Replication in Hot Standby with read heavy Slave
- terminating connection due to conflict with recovery, user was holding a relation lock for too long
- Setting hot standby feedback for a specific query in PostgreSQL
- Re: Making WAL receiver startup rely on GUC context for primary_conninfo and primary_slot_name
- Minimal logical decoding on standbys
- Re: Can I skip function ResolveRecoveryConflictWithSnapshot if setting hot_standby_feedback=on all the time
- Re: Minimal logical decoding on standbys
- Re: Sketch of a fix for that truncation data corruption issue