Ian Barwick ba1f05ece9
Restrict "node_name" to maximum 63 characters ...
In "recovery.conf", the configuration parameter "node_name" is used
as the "application_name" value, which will be truncated by PostgreSQL
to 63 characters (NAMEDATALEN - 1).
repmgr sometimes needs to be able to extract the application name from
pg_stat_replication to determine if a node is connected (e.g. when
executing "repmgr standby register"), so the comparison will fail
if "node_name" exceeds 63 characters.
2019-03-28 10:37:57 +09:00
2017-12-21 18:31:05 +00:00
2019-02-24 12:44:10 +07:00
2019-02-01 13:13:11 +09:00
2019-03-27 14:22:55 +09:00
2018-08-30 12:40:05 +09:00
2019-02-08 15:28:12 +09:00
2019-01-23 10:28:48 +09:00
2019-01-23 10:28:48 +09:00
2019-02-22 13:52:02 +09:00
2018-07-12 14:50:48 +09:00
2019-03-28 10:37:57 +09:00
2018-11-28 12:58:07 +09:00
2019-03-15 14:39:37 +09:00
2019-01-23 12:25:02 +09:00
2019-02-27 13:01:19 +09:00
2019-03-20 16:31:52 +09:00
2019-01-21 17:37:01 +05:30
2019-01-30 09:45:08 +09:00
2019-01-07 12:18:17 +09:00
2019-03-21 10:30:00 +09:00
2017-10-17 11:00:37 +09:00
2019-01-21 14:54:35 +09:00
2019-03-15 16:29:31 +09:00
2018-04-24 21:08:05 +09:00
2017-10-19 12:21:50 +09:00
2019-01-23 12:25:02 +09:00
2018-09-25 15:56:40 +09:00
2019-02-05 11:06:26 +09:00
2018-07-13 11:19:42 +09:00
2019-02-05 11:06:26 +09:00
2019-03-18 10:49:38 +09:00
2019-02-05 11:06:26 +09:00
2019-02-11 10:55:10 +09:00
2019-02-28 12:27:39 +09:00
2019-02-11 10:55:10 +09:00
2019-02-05 11:06:26 +09:00
2019-02-23 10:09:43 +09:00
2019-02-05 11:06:26 +09:00
2019-02-05 11:06:26 +09:00
2019-02-05 11:06:26 +09:00
2018-10-31 10:27:37 +09:00
2018-08-30 12:39:58 +09:00
2019-01-29 13:01:19 +09:00
2019-02-12 17:24:56 +09:00
2019-03-14 11:58:31 +08:00
2018-08-30 12:39:58 +09:00
2019-02-12 16:39:13 +09:00
2018-08-30 12:39:58 +09:00
2019-02-04 14:45:32 +09:00
2018-08-30 12:39:58 +09:00
2019-03-20 16:31:52 +09:00
2019-03-20 16:31:52 +09:00
2018-08-30 12:39:54 +09:00
2019-03-22 15:43:55 +09:00
2017-08-25 15:58:52 +09:00
2019-03-13 16:12:11 +09:00
2019-03-22 15:43:55 +09:00
2017-10-05 10:30:28 +09:00
2017-10-05 10:30:28 +09:00
2019-02-05 16:32:39 +09:00
2019-01-23 10:28:48 +09:00
2019-01-15 12:45:33 +09:00
2017-10-05 10:30:29 +09:00
ba1f05ece9