SLONIK RESTART NODE

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.

Example

  RESTART NODE ( ID = 2 );
    

Locking Behaviour

No application-visible locking should take place.

Slonik Event Confirmation Behaviour

Slonik does not wait for event confirmations before performing this command

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.