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.
This setting does not override the behavior of old_snapshot_threshold on the primary; a snapshot on the standby which exceeds the primary's age threshold can become invalid, resulting in cancellation of transactions on the standby. This is because old_snapshot_threshold is intended to provide an absolute limit on the time which dead rows can contribute to bloat, which would otherwise be violated because of the configuration of a standby.
- Are there any performance effects on master when using postgres streaming replication with hot_standby_feedback on
- Is hot_standby_feedback needed when using PostgreSQL 10 logical replication?
- How can I fix PostgreSQL canceling statement error on Google SQL?
- Setting hot standby feedback for a specific query in PostgreSQL
- terminating connection due to conflict with recovery, user was holding a relation lock for too long
- Re: TRAP: FailedAssertion("!(TransactionIdPrecedesOrEquals
- Re: [HACKERS] Why forcing Hot_standby_feedback to be enabled when creating a logical decoding slot on standby
- Re: let's make the list of reportable GUCs configurable (was Re: Add %r substitution for psql prompts to show recovery status)
- Re: [HACKERS] make async slave to wait for lsn to be replayed
- Re: [HACKERS] [PATCH v1] Add and report the new "in_hot_standby" GUC pseudo-variable.