Dimitri Fontaine wrote:
> 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.
max_standby_delay=-1 does that. The documentation needs to be updated to
reflect that, it currently says:
> There is no wait-forever setting because of the potential for deadlock which that setting would introduce. This parameter can only be set in the postgresql.conf file or on the server command line.
but that is false, -1 means wait forever. Simon removed that option at
one point, but it was later put back and apparently the documentation
was never updated.
In response to
pgsql-hackers by date
|Next:||From: Heikki Linnakangas||Date: 2010-02-27 09:33:34|
|Subject: Re: Hot Standby query cancellation and Streaming Replication
|Previous:||From: Heikki Linnakangas||Date: 2010-02-27 09:00:42|
|Subject: Re: visibility maps and heap_prune|