DROP NODE — Remove the node from participating in the replication
DROP NODE (options);
Drop a node. This command removes the specified node entirely from the replication systems configuration. If the replication daemon is still running on that node (and processing events), it will attempt to uninstall the replication system and terminate itself.
ID = ival
Node ID of the node to remove.
EVENT NODE = ival
Node ID of the node to generate the event; default is 1.
This uses schemadocdropnode( integer ).
When you invoke DROP NODE
, one of the
steps is to run UNINSTALL NODE
.
When dropping triggers off of application tables, this will require exclusive access to each replicated table on the node being discarded.
If you are using connections that cache query plans
(this is particularly common for Java application frameworks with
connection pools), the connections may cache query plans that
include the pre-DROP NODE
state of things, and
you will get error messages indicating missing OIDs.
After dropping a node, you may also need to recycle connections in your application.
You cannot submit this to an EVENT
NODE
that is the number of the node being dropped; the
request must go to some node that will remain in the
cluster.