Provided by: slony1-2-doc_2.0.7-3build1_all bug


       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.

       This uses “schemadocdropnode(integer)” [not available as a man page].

       When you invoke DROP NODE, one of the steps is to run UNINSTALL NODE.


            DROP NODE ( ID = 2, EVENT NODE = 1 );


       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 [“[MISSING TEXT]” [not available as a man page]].

       After dropping a node, you may also need to recycle connections in your

       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


       This command was introduced in Slony-I 1.0

       In version 2.0, the default value for EVENT NODE was removed, so a node
       must be specified.

                                3 December 2011            SLONIK DROP NODE(7)