'\" -*- 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 RESTART NODE" 7 "24 July 2014" "" "Slony-I 2.2.3 Documentation"
.SH NAME
RESTART NODE \- Restart Slony-I node 
.SH SYNOPSIS
'nh
.fi
.ad l
\fBRESTART 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
Causes an eventually running replication daemon
(slon process) on the specified node to
shutdown and restart itself. Theoretically, this command should
be obsolete. In practice, TCP timeouts can delay critical
configuration changes to actually happen in the case where a
former forwarding node failed and needs to be bypassed by
subscribers.
.TP 
\*(T<ID = ival \*(T>
Node ID of the node to restart.
.SH EXAMPLE
.nf
\*(T<  RESTART NODE ( ID = 2 );
    \*(T>
.fi
.SH "LOCKING BEHAVIOUR "
No application-visible locking should take place. 
.SH "SLONIK EVENT CONFIRMATION BEHAVIOUR "
Slonik does not wait for event confirmations before 
performing this command
.SH "VERSION INFORMATION "
This command
was introduced in Slony-I 1.0; frequent use became unnecessary as
of version 1.0.5. There are, however, occasional cases where it is
necessary to interrupt a slon process,
and this allows this to be scripted via slonik.