github/repmgr
1
0
Fork 0
mirror of https://github.com/EnterpriseDB/repmgr.git synced 2026-03-26 08:36:30 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

docs: fix example in BDR section

Browse Source
This commit is contained in:
Ian Barwick
2017-11-02 11:23:41 +09:00
parent 91531bffe4
commit 60e877ca39
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
doc/repmgrd-bdr.sgml
View File

@@ -154,8 +154,9 @@
</para> </para>
<para> <para>
Additionally it's possible to display log of significant events; executing Additionally it's possible to display log of significant events; executing
<xref linkend="repmgr-cluster-show"> (on either node) should produce output like this: <xref linkend="repmgr-cluster-event"> (on either node) should produce output like this:
<programlisting> <programlisting>
$ repmgr -f /etc/repmgr.conf cluster event
Node ID | Event | OK | Timestamp | Details Node ID | Event | OK | Timestamp | Details
---------+--------------+----+---------------------+---------------------------------------------- ---------+--------------+----+---------------------+----------------------------------------------
2 | bdr_register | t | 2017-07-27 17:51:48 | node record created for node 'node2' (ID: 2) 2 | bdr_register | t | 2017-07-27 17:51:48 | node record created for node 'node2' (ID: 2)
@@ -163,8 +164,8 @@
</programlisting> </programlisting>
</para> </para>
<para> <para>
At this point there will only be records for the two node registrations (displayed in reverse At this point there will only be records for the two node registrations (displayed here
chronological order). in reverse chronological order).
</para> </para>
</sect1> </sect1>