Skip to content

Commit e5bc71c

Browse files
authored
Fix documentation of health_check_period to match code (#926)
1 parent 54fafca commit e5bc71c

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

docs/fault-tolerance.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ every PostgreSQL node it manages. A health-check is successful when it is
2222
able to connect to the PostgreSQL node using the PostgreSQL protocol
2323
(libpq), imitating the ``pg_isready`` command.
2424

25-
How frequent those health checks are (20s by default), the PostgreSQL
25+
How frequent those health checks are (5s by default), the PostgreSQL
2626
connection timeout in use (5s by default), and how many times to retry in
2727
case of a failure before marking the node unhealthy (2 by default) are GUC
2828
variables that you can set on the Monitor node itself. Remember, the monitor
@@ -35,7 +35,7 @@ PostgreSQL configuration settings::
3535
name | setting
3636
-----------------------------------------+---------
3737
pgautofailover.health_check_max_retries | 2
38-
pgautofailover.health_check_period | 20000
38+
pgautofailover.health_check_period | 5000
3939
pgautofailover.health_check_retry_delay | 2000
4040
pgautofailover.health_check_timeout | 5000
4141
(4 rows)

0 commit comments

Comments
 (0)