Drop Down MenusCSS Drop Down MenuPure CSS Dropdown Menu

Slony-I tasks

In the appropriate context, pgAdmin III can trigger several maintenance tasks.
  • Restart node - Under some conditions, it may be necessary to restart a slon process on a node, initialize as if freshly started and make it reload its configuration. This can be triggered remotely with the restart node function.
  • Lock set - Disables updates to a set to be replicated. This is necessary for clean switch over the source of a replication from one node to another.
  • Unlock set - Re-enables updates to a set to be replicated after a previous lock.
  • Merge set - Joins two sets, originating from the same node and subscribed by the same nodes, into one. This can be used as a workaround to the fact that a subscribed set can’t be extended.
  • Move set - Moves a replication set from one node to another, i.e. making the target node the new source. The old node will become subscriber to the new provider node. This is the normal way how to switch over gracefully the master role from one node to another.


Popular posts from this blog

7 Steps to configure BDR replication in postgresql


How to find the server is whether standby (slave) or primary(master) in Postgresql replication ?

How to Get Table Size, Database Size, Indexes Size, schema Size, Tablespace Size, column Size in PostgreSQL Database

ORA-01261: Parameter db_recovery_file_dest destination string cannot be translated ORA-01262: Stat failed on a file destination directory Linux-x86_64 Error: 2: No such file or directory