Re: Keepalive for max_standby_delay

Поиск
Список
Период
Сортировка
От Heikki Linnakangas
Тема Re: Keepalive for max_standby_delay
Дата
Msg-id 4BF301BD.6060102@enterprisedb.com
обсуждение исходный текст
Ответ на Re: Keepalive for max_standby_delay  (Jim Nasby <decibel@decibel.org>)
Ответы Re: Keepalive for max_standby_delay  (Simon Riggs <simon@2ndQuadrant.com>)
Список pgsql-hackers
On 17/05/10 12:36, Jim Nasby wrote:
> On May 15, 2010, at 12:05 PM, Heikki Linnakangas wrote:
>> What exactly is the user trying to monitor? If it's "how far behind is
>> the standby", the difference between pg_current_xlog_insert_location()
>> in the master and pg_last_xlog_replay_location() in the standby seems
>> more robust and well-defined to me. It's a measure of XLOG location (ie.
>> bytes) instead of time, but time is a complicated concept.
>
> I can tell you that end users *will* want a time-based indication of how far behind we are. DBAs will understand
"we'rethis many transactions behind", but managers and end users won't. Unless it's unreasonable to provide that info,
weshould do so.
 

No doubt about that, the problem is that it's hard to provide a reliable 
time-based indication.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Jesper Krogh
Дата:
Сообщение: Re: pg_upgrade - link mode and transaction-wraparound data loss
Следующее
От: Alex Hunsaker
Дата:
Сообщение: Re: BYTEA / DBD::Pg change in 9.0 beta