| From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: timestamp of the last replayed transaction |
| Date: | 2010-11-02 13:38:27 |
| Message-ID: | m2vd4f4zho.fsf@2ndQuadrant.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Fujii Masao <masao(dot)fujii(at)gmail(dot)com> writes:
> After 9.0 release, I've often heard that some people want to know
> how far transactions have been replayed in the standby in timestamp
> rather than LSN. So I'm thinking to include the function which returns
> the timestamp of the last applied transaction (i.e., commit/abort WAL
> record) in the core.
>
> Name: pg_last_replay_xact_timestamp (better name?)
> Return Type: timestamp with time zone
>
> Thought?
How do you want to implement the tracking? Will it look like the
proposal in this thread:
http://archives.postgresql.org/pgsql-hackers/2010-05/msg01209.php
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-11-02 14:04:10 | Re: [PATCH] Custom code int(32|64) => text conversions out of performance reasons |
| Previous Message | Dimitri Fontaine | 2010-11-02 13:03:44 | Re: ALTER OBJECT any_name SET SCHEMA name |