From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Function to know last log write timestamp |
Date: | 2014-08-11 01:35:29 |
Message-ID: | CAHGQGwGwA6LLUFhBGxr5b8g5j4oBKipU5JsanGLH2GA124S7_A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Aug 11, 2014 at 9:23 AM, Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:
> We can know the LSN of last committed WAL record on primary by using
> pg_current_xlog_location(). It seems there's no API to know the time
> when the WAL record was created. I would like to know standby delay by
> using pg_last_xact_replay_timestamp() and such that API.
>
> If there's no such a API, it would be useful to invent usch an API IMO.
+1
I proposed that function before, but unfortunately it failed to be applied.
But I still think that function is useful to calculate the replication delay.
The past discussion is
http://www.postgresql.org/message-id/CAHGQGwF3ZjfuNEj5ka683KU5rQUBtSWtqFq7g1X0g34o+JXWBw@mail.gmail.com
Regards,
--
Fujii Masao
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2014-08-11 01:48:07 | Re: Function to know last log write timestamp |
Previous Message | Tatsuo Ishii | 2014-08-11 00:23:05 | Function to know last log write timestamp |