Add monitoring function pg_last_xact_replay_timestamp.

Fujii Masao, with a little wordsmithing by me.

1 files changed, 19 insertions, 0 deletions

diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 183b72cda48..1be9f90fe5e 100644
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -13551,6 +13551,9 @@ postgres=# SELECT * FROM pg_xlogfile_name_offset(pg_stop_backup());
    <indexterm>
     <primary>pg_last_xlog_replay_location</primary>
    </indexterm>
+   <indexterm>
+    <primary>pg_last_xact_replay_timestamp</primary>
+   </indexterm>
 
    <para>
     The functions shown in <xref
@@ -13605,6 +13608,22 @@ postgres=# SELECT * FROM pg_xlogfile_name_offset(pg_stop_backup());
         the function returns NULL.
        </entry>
       </row>
+      <row>
+       <entry>
+        <literal><function>pg_last_xact_replay_timestamp()</function></literal>
+        </entry>
+       <entry><type>timestamp with time zone</type></entry>
+       <entry>Get timestamp of last transaction replayed during recovery.
+        This is the time at which the commit or abort WAL record for that
+        transaction was generated.
+        If no transactions have been replayed during recovery, this function
+        returns NULL.  Otherwise, if recovery is still in progress this will
+        increase monotonically.  If recovery has completed then this value will
+        remain static at the value of the last transaction applied during that
+        recovery.  When the server has been started normally without recovery
+        the function returns NULL.
+       </entry>
+      </row>
      </tbody>
     </tgroup>
    </table>