Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Doesn't the system already adjust the delay based on the length of slave
> transactions, e.g. max_standby_delay. It seems there is no need for a
> user switch --- just max_standby_delay really high.
Well that GUC looks like it allows to set a compromise between HA and
reporting, not to say "do not ever give the priority to the replay while
I'm running my reports". At least that's how I understand it.
The feedback loop might get expensive on master server when running
reporting queries on the slave, unless you can "pause" it explicitly I
think. I don't see how the system will guess that you're running a
reporting server rather than a HA node, and max_standby_delay is just a
way to tell the standby to please be nice in case of abuse.
In response to
pgsql-hackers by date
|Next:||From: Bruce Momjian||Date: 2010-02-26 22:20:37|
|Subject: Re: Hot Standby query cancellation and Streaming
|Previous:||From: Gokulakannan Somasundaram||Date: 2010-02-26 21:48:42|
|Subject: Re: A thought on Index Organized Tables|