'\" -*- coding: us-ascii -*-
.if \n(.g .ds T< \\FC
.if \n(.g .ds T> \\F[\n[.fam]]
.de URL
\\$2 \(la\\$1\(ra\\$3
..
.if \n(.g .mso www.tmac
.TH "SLONIK DROP NODE" 7 "24 July 2014" "" "Slony-I 2.2.3 Documentation"
.SH NAME
DROP NODE \- Remove the node from participating in the replication 
.SH SYNOPSIS
'nh
.fi
.ad l
\fBDROP NODE (options);\fR \kx
.if (\nx>(\n(.l/2)) .nr x (\n(.l/5)
'in \n(.iu+\nxu
'in \n(.iu-\nxu
.ad b
'hy
.SH DESCRIPTION
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.
.TP 
\*(T<ID = ival \*(T>
Node ID of the node to remove. This may be
represented either by a single node id or by a
quoted comma separated list of nodes 
.TP 
\*(T<EVENT NODE = ival \*(T>
Node ID of the node to generate the event.
.PP
This uses \(lqschemadocdropnode(p_no_ids integer[])\(rq [not available as a man page]. 
.PP
When you invoke \fBDROP NODE\fR, one of the
steps is to run \fBUNINSTALL NODE\fR.
.SH EXAMPLE
.nf
\*(T<     DROP NODE ( ID = 2, EVENT NODE = 1 );
	 DROP NODE (ID='3,4,5', EVENT NODE=1);
    \*(T>
.fi
.SH "LOCKING BEHAVIOUR "
When dropping triggers off of application tables, this will
require exclusive access to each replicated table on the node
being discarded.
.SH "DANGEROUS/UNINTUITIVE BEHAVIOUR"
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-\fBDROP NODE\fR state of things, and
you will get error messages indicating missing OIDs [\(lq[MISSING TEXT]\(rq [not available as a man page]].
.PP
After dropping a node, you may also need to recycle
connections in your application.
.PP
You cannot submit this to an \fBEVENT
NODE\fR that is the number of the node being dropped; the
request must go to some node that will remain in the
cluster. 
.SH "SLONIK EVENT CONFIRMATION BEHAVIOUR "
Slonik waits until nodes (other than the one being dropped)
are caught up with non-SYNC events from all other nodes before
submitting the DROP NODE command.
.SH "VERSION INFORMATION "
This command was introduced in Slony-I 1.0 
.PP
In version 2.0, the default value for \fBEVENT NODE\fR was removed, so a node must be specified.
.PP
In version 2.2, support for dropping multiple nodes in a single
command was introduced