Man page - pcp_detach_node(1)
Packages contains this manual
- pcp_invalidate_query_cache(1)
- pgpool_adm_pcp_node_count(3)
- pcp_proc_info(1)
- pcp_recovery_node(1)
- pcp_common_options(1)
- pgpool_adm_pcp_pool_status(3)
- pcp_proc_count(1)
- pcp_log_rotate(1)
- pgpool_adm_pcp_node_info(3)
- pgpool_adm_pcp_attach_node(3)
- pcp_stop_pgpool(1)
- pcp_node_count(1)
- pgpool_setup(1)
- pcp_health_check_stats(1)
- pgpool_adm_pcp_detach_node(3)
- pgpool_adm_pcp_health_check_stats(3)
- pg_md5(1)
- pcp_promote_node(1)
- pcp_pool_status(1)
- pcp_detach_node(1)
- wd_cli(1)
- pg_enc(1)
- pcp_reload_config(1)
- pgpool_adm_pcp_proc_info(3)
- pcp_watchdog_info(1)
- pgproto(1)
- pgpool(8)
- watchdog_setup(1)
- pcp_node_info(1)
- pcp_attach_node(1)
apt-get install pgpool2
Manual
PCP_DETACH_NODE
NAMESYNOPSIS
DESCRIPTION
OPTIONS
NAME
pcp_detach_node - detaches the given node from Pgpool-II. Existing connections to Pgpool-II are forced to be disconnected.
SYNOPSIS
|
pcp_detach_node [ options ...] [ node_id ] [ gracefully ] |
DESCRIPTION
pcp_detach_node detaches the given node from Pgpool-II. If failover_command and/or follow_primary_command are specified, they are executed too. Existing connections to Pgpool-II are forced to be disconnected.
pcp_detach_node just detaches the node, and does not touch running backend behind the node. This command is useful when admin needs to maintain the PostgreSQL node. He/she can shutdown or stop the backend as many times as he/she wants.
The safest way to re-attach the detached node is, stopping the backend and apply pcp_recovery_node (1). However if you are sure that there's no replication delay (or the delay will be recovered later on) and the role of the node (primary/standby) will not be changed, you can use pcp_attach_node (1).
OPTIONS
-n
node_id
--node_id=
node_id
The index of backend node to detach.
-g
--gracefully
wait until all clients are disconnected (unless client_idle_limit_in_recovery is -1 or recovery_timeout is expired).
Other options
See pcp_common_options (1).