'\" -*- 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 SET" 7 "24 July 2014" "" "Slony-I 2.2.3 Documentation"
.SH NAME
DROP SET \- Discard Slony-I replication set 
.SH SYNOPSIS
'nh
.fi
.ad l
\fBDROP SET (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 set of tables from the Slony-I
configuration. This automatically unsubscribes all nodes from the
set and restores the original triggers and rules on all
subscribers.
.TP 
\*(T<ID = ival \*(T>
ID of the set to be dropped.
.TP 
\*(T<ORIGIN = ival \*(T>
Current origin node of the set.
.PP
This uses \(lqschemadocdropset(p_set_id integer)\(rq [not available as a man page]. 
.SH EXAMPLE
.nf
\*(T<  DROP SET ( ID = 5, 
             ORIGIN = 2 );
    \*(T>
.fi
.SH "LOCKING BEHAVIOUR "
On each node, this will require taking out exclusive locks
on each replicated table in order to modify the table schema to
clean up the triggers and rules. 
.SH "SLONIK EVENT CONFIRMATION BEHAVIOUR "
Slonik waits for the command submitted to the previous
event node to be confirmed on the specified event node before
submitting this command.
.SH "VERSION INFORMATION "
This command was introduced in Slony-I 1.0