On 2016-11-28 22:14:55 +0100, Torsten Förtsch wrote:
> Hi,
>
> I am in the process of reviewing our configs for a number of 9.3 databases
> and found a replica with hot_standby_feedback=on. I remember when we set it
> long ago we were fighting cancelled queries. I also remember that it never
> rea
Hi,
I am in the process of reviewing our configs for a number of 9.3 databases
and found a replica with hot_standby_feedback=on. I remember when we set it
long ago we were fighting cancelled queries. I also remember that it never
really worked for us. In the end we set up 2 replicas, one suitable
Thank you for the guidance! So far so good with
max_standby_archive/streaming_delay, no cancellations.
Steve Kehlet wrote:
> 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.
>
> Whi
On 8/21/2014 1:44 PM, Steve Kehlet wrote:
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
On 08/21/2014 03:44 PM, Steve Kehlet wrote:
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 remem
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 b
On Thu, Aug 29, 2013 at 2:44 PM, Tatsuo Ishii wrote:
> I have a question about hot_standby_feedback parameter. In my
> understanding, if this parameter is on, a long running transaction on
> standby will not be canceled even if the transaction conflicts.
> As you can see vacuum on the primary rem
I have a question about hot_standby_feedback parameter. In my
understanding, if this parameter is on, a long running transaction on
standby will not be canceled even if the transaction conflicts.
So I have primary PostgreSQL and standby PostgreSQL running 9.2.4.
On primary:
create table t1(i int)
