hot_standby_feedback vs. max_standby_archive_delay/max_standby_streaming_delay? - Mailing list pgsql-general

From Steve Kehlet
Subject hot_standby_feedback vs. max_standby_archive_delay/max_standby_streaming_delay?
Date
Msg-id CA+bfosH-Amf5T7YPE=2X7K9LmWL+zQpkdMAsgtQeA2THL7Aimg@mail.gmail.com
Whole thread Raw
Responses Re: hot_standby_feedback vs. max_standby_archive_delay/max_standby_streaming_delay?  (Shaun Thomas <sthomas@optionshouse.com>)
Re: hot_standby_feedback vs. max_standby_archive_delay/max_standby_streaming_delay?  (John R Pierce <pierce@hogranch.com>)
Re: hot_standby_feedback vs. max_standby_archive_delay/max_standby_streaming_delay?  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-general
Our queries on our Standby are getting cancelled and so we're investigating how to prevent this. The standby is for running periodic reporting queries only, we don't care if it falls behind a little bit, we just set this guy up to reduce the load on the Primary.

While researching there appear to be several different parameters that can help solve this. It sounds like we don't need hot_standby_feedback or vacuum_defer_cleanup_age, we really just want to pause things on the standby to let it run its queries. So we're going to try applying max_standby_archive_delay and max_standby_streaming_delay to 1h or so. We're also looking at pg_xlog_replay_pause(), although this is less desirable because we don't want to have to ask the people running reports to remember to pause and resume things.

Can anyone confirm we're on the right track or provide further guidance? Thanks so much.

pgsql-general by date:

Previous
From: Alban Hertroys
Date:
Subject: Re: Does writing new records while massive update will generate lock ?
Next
From: Shaun Thomas
Date:
Subject: Re: hot_standby_feedback vs. max_standby_archive_delay/max_standby_streaming_delay?