Re: Checking for stale reads on hot standby
От | Fujii Masao |
---|---|
Тема | Re: Checking for stale reads on hot standby |
Дата | |
Msg-id | AANLkTi=jgnO5neqzcoJ3+zjuP0Z5BxMFv0+DcxG+SGCo@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Checking for stale reads on hot standby (Gurjeet Singh <singh.gurjeet@gmail.com>) |
Ответы |
Re: Checking for stale reads on hot standby
|
Список | pgsql-general |
On Mon, Sep 27, 2010 at 9:09 AM, Gurjeet Singh <singh.gurjeet@gmail.com> wrote: > See the nuggets hidden in section 25.2.5.2. "Monitoring" at > http://www.postgresql.org/docs/9.0/static/warm-standby.html#STREAMING-REPLICATION > > After an UPDATE, your application can cache the info from > 'pg_current_xlog_location()' result on the primary and then compare that > with the result of 'pg_last_xlog_receive_location()' on the standby to see > if it is seeing fresh enough data. Yep, but since recovery might fall behind WAL receiving, pg_last_xlog_replay_location should be called instead of pg_last_xlog_receive_location. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center
В списке pgsql-general по дате отправления: