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

Don't issue a CHECKPOINT after promoting a standby.

Browse Source 
Issuing a CHECKPOINT immediately after promoting a standby may impact
performance. Commit 239a548e9d ensures
one is only issued when required, i.e. during a switchover when
pg_rewind will be executed.

This reverts commit a2068768ab.
This commit is contained in:
Ian Barwick
2018-04-09 14:35:54 +09:00
parent b9dc94f28f
commit 62c29aab32
1 changed files with 0 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
repmgr-action-standby.c
View File

@@ -2043,13 +2043,6 @@ _do_standby_promote_internal(PGconn *conn, const char *data_dir)
log_verbose(LOG_INFO, _("standby promoted to primary after %i second(s)"), i); log_verbose(LOG_INFO, _("standby promoted to primary after %i second(s)"), i);
/*
* Execute a CHECKPOINT as soon as possible after promotion. The primary
* reason for this is to ensure that "pg_control" has the latest timeline
* before it's read by "pg_rewind", typically during a switchover operation.
*/
checkpoint(conn);
/* update node information to reflect new status */ /* update node information to reflect new status */
if (update_node_record_set_primary(conn, config_file_options.node_id) == false) if (update_node_record_set_primary(conn, config_file_options.node_id) == false)
{ {