|ID = ival|
|Node ID of the node to uninstall.|
The difference between UNINSTALL NODE and DROP NODE is that all UNINSTALL NODE does is to remove the Slony-I configuration; it doesnt drop the nodes configuration from replication.
UNINSTALL NODE ( ID = 2 );
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-UNINSTALL 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.
Slonik does not wait for event confirmations before performing this command
This command was introduced in Slony-I 1.0
|SLONIK UNINSTALL NODE (7)||18 January 2015|