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

Miscelleanous comment fixes

Browse Source
This commit is contained in:
Ian Barwick
2015-09-25 11:17:26 +09:00
parent c3bd02b83d
commit 45eb0ea5d3
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
dbutils.c
View File

@@ -1146,8 +1146,8 @@ delete_node_record(PGconn *conn, int node, char *action)
* *
* Note this function may be called with `conn` set to NULL in cases where * Note this function may be called with `conn` set to NULL in cases where
* the master node is not available and it's therefore not possible to write * the master node is not available and it's therefore not possible to write
* an event record. In this case, if `event_notification_command` is set a user- * an event record. In this case, if `event_notification_command` is set, a
* defined notification to be generated; if not, this function will have * user-defined notification to be generated; if not, this function will have
* no effect. * no effect.
*/ */
@@ -1160,7 +1160,7 @@ create_event_record(PGconn *conn, t_configuration_options *options, int node_id,
bool success = true; bool success = true;
struct tm ts; struct tm ts;
/* Only attempt to write a record if a connection handle was provided/ /* Only attempt to write a record if a connection handle was provided.
Also check that the repmgr schema has been properly intialised - if Also check that the repmgr schema has been properly intialised - if
not it means no configuration file was provided, which can happen with not it means no configuration file was provided, which can happen with
e.g. `repmgr standby clone`, and we won't know which schema to write to. e.g. `repmgr standby clone`, and we won't know which schema to write to.