pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alexander Fortin <alexander.fortin@gmail.com>
To: Sergey Konoplev <gray.ru@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Interpreting pg_stat_replication values
Date: Thu, 19 Jan 2012 16:04:30 +0100
Message-ID: <4F1830FE.3030005@gmail.com> (raw)
In-Reply-To: <CAL_0b1vJZdJtGLzBN_wRDoqUCAG6MuF_rCVELgvw+isSehoAUw@mail.gmail.com>
References: <4F13ED11.6080001@gmail.com>
	<CAL_0b1vJZdJtGLzBN_wRDoqUCAG6MuF_rCVELgvw+isSehoAUw@mail.gmail.com>

On 1/18/12 9:38 AM, Sergey Konoplev wrote:
> With 9.1 you can use
>
> SELECT now() - pg_last_xact_replay_timestamp() AS time_lag;

Hi Sergey,
thank you very much for your suggestion. In the meanwhile we went for a 
check on pg_stat_replication, but we'll add one as you suggest soon on 
the replicas.

By the way, maybe you know where I could find documentation about 
possible values from column "state" on view pg_stat_replication? I can 
see "streaming" when everything is ok, and once I could get just a 
"catchup" while a replica was synching.

-- 
Alexander Fortin
http://about.me/alexanderfortin/



view thread (4+ messages)  latest in thread

Message-ID: <4F1830FE.3030005@gmail.com>
Permalink:  ../4F1830FE.3030005@gmail.com/
Also on:    postgresql.org/message-id/4F1830FE.3030005@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: alexander.fortin@gmail.com, gray.ru@gmail.com
  Subject: Re: Interpreting pg_stat_replication values
  In-Reply-To: <4F1830FE.3030005@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox