SVN Commit by dpage: r4894 - trunk/pgadmin3/docs/en_US - Mailing list pgadmin-hackers
| From | svn@pgadmin.org |
|---|---|
| Subject | SVN Commit by dpage: r4894 - trunk/pgadmin3/docs/en_US |
| Date | |
| Msg-id | 200601121411.k0CEBSDQ024137@developer.pgadmin.org Whole thread Raw |
| List | pgadmin-hackers |
Author: dpage
Date: 2006-01-12 14:11:28 +0000 (Thu, 12 Jan 2006)
New Revision: 4894
Modified:
trunk/pgadmin3/docs/en_US/slony-functions.html
trunk/pgadmin3/docs/en_US/slony-install.html
trunk/pgadmin3/docs/en_US/slony-path.html
trunk/pgadmin3/docs/en_US/slony-set.html
Log:
Tweak HTML
Modified: trunk/pgadmin3/docs/en_US/slony-functions.html
===================================================================
--- trunk/pgadmin3/docs/en_US/slony-functions.html 2006-01-12 14:06:53 UTC (rev 4893)
+++ trunk/pgadmin3/docs/en_US/slony-functions.html 2006-01-12 14:11:28 UTC (rev 4894)
@@ -12,25 +12,25 @@
In the appropriate context, pgAdmin III can trigger several maintenance tasks.
<UL>
<LI><P>
- <b id='restart'>Restart node</b> - Under some conditions, it may be necessary
+ <b id="restart">Restart node</b> - 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.
</P>
<LI><P>
- <b id='lock'>Lock set</b> - Disables updates to a set to be replicated. This is
+ <b id="lock">Lock set</b> - 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.
</P>
<LI><P>
- <b id='unlock'>Unlock set</b> - Re-enables updates to a set to be replicated
+ <b id="unlock">Unlock set</b> - Re-enables updates to a set to be replicated
after a previous lock.
</P>
<LI><P>
- <b id='merge'>Merge set</b> - Joins two sets, originating from the same node
+ <b id="merge">Merge set</b> - 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.
</P>
<LI><P>
- <b id='move'>Move set</b> - Moves a replication set from one node to another,
+ <b id="move">Move set</b> - 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.
Modified: trunk/pgadmin3/docs/en_US/slony-install.html
===================================================================
--- trunk/pgadmin3/docs/en_US/slony-install.html 2006-01-12 14:06:53 UTC (rev 4893)
+++ trunk/pgadmin3/docs/en_US/slony-install.html 2006-01-12 14:11:28 UTC (rev 4894)
@@ -7,7 +7,7 @@
</head>
<body>
-<A name='node'/>
+<A name="node"></a>
<h3>Slony-I administration with pgAdmin III: installation</h3>
<BR>
<H4>Prerequisites</H4>
@@ -16,8 +16,8 @@
xxid and slony1_funcs must be present on all servers that have are to run a
Slony-I replication node. This is usually done by the Slony-I installation routine.
</p>
-<BR><BR><BR>
-<A name='create'/>
+
+<A name="create">
<H4>Create cluster and first node</H4>
<BR>
<center><img src="images/slony-create.png"></center>
@@ -32,8 +32,8 @@
To achieve this, pgAdmin III uses the concept of "Administrative nodes".
</p>
-<BR><BR><BR>
-<A name='join'/>
+
+<A name="join">
<H4>Join additional nodes to cluster</H4>
<BR>
<center><img src="images/slony-join.png"></center>
@@ -48,8 +48,8 @@
<A href='"slony-path.html'>replication paths</A> between the nodes, to enable communication
between the nodes.
</p>
-<BR><BR><BR>
-<A name='upgrade'/>
+
+<A name="upgrade">
<H4>Upgrade node to new cluster software</H4>
<BR>
<center><img src="images/slony-upgrade.png"></center>
Modified: trunk/pgadmin3/docs/en_US/slony-path.html
===================================================================
--- trunk/pgadmin3/docs/en_US/slony-path.html 2006-01-12 14:06:53 UTC (rev 4893)
+++ trunk/pgadmin3/docs/en_US/slony-path.html 2006-01-12 14:11:28 UTC (rev 4894)
@@ -8,8 +8,8 @@
<body>
<h3>Creating paths and listens</h3>
-<BR><BR><BR>
-<A name='path'/>
+
+<A name="path">
<H4>Create paths to other nodes</H4>
<BR>
<center><img src="images/slony-path.png"></center>
@@ -20,8 +20,8 @@
Usually, you will need to specify host, dbname and username, while the password should
be stored in the <a href='pg/libpq-pgpass.html'>.pgpass file</A>.
</p>
-<BR><BR><BR>
-<A name='listen'/>
+
+<A name="listen">
<H4>Create listens to other nodes</H4>
<BR>
<center><img src="images/slony-listen.png"></center>
Modified: trunk/pgadmin3/docs/en_US/slony-set.html
===================================================================
--- trunk/pgadmin3/docs/en_US/slony-set.html 2006-01-12 14:06:53 UTC (rev 4893)
+++ trunk/pgadmin3/docs/en_US/slony-set.html 2006-01-12 14:11:28 UTC (rev 4894)
@@ -9,8 +9,8 @@
<body>
<h3>Creating sets and subscriptions</h3>
-<BR><BR><BR>
-<A name='set'/>
+
+<A name="set"></a>
<H4>Create replication set</H4>
<BR>
<center><img src="images/slony-set.png"></center>
@@ -18,8 +18,8 @@
Slony-I groups tables and sequences it has to replicate from a master to slaves into
replication sets. The set is created on the source node of the data.
</p>
-<BR><BR><BR>
-<A name='table'/>
+
+<A name="table"></a>
<H4>Define replicated table</H4>
<BR>
<center><img src="images/slony-table.png"></center>
@@ -40,16 +40,16 @@
with tables added to replication sets with pgAdmin III. We strongly recommend defining
a primary key on the tables to be replicated.
</p>
-<BR><BR><BR>
-<A name='sequence'/>
+
+<A name="sequence"></a>
<H4>Define replicated sequence</H4>
<BR>
<center><img src="images/slony-sequence.png"></center>
<p>
The sequence allows adding sequences to a replication set.
</p>
-<BR><BR><BR>
-<A name='subscription'/>
+
+<A name="subscription">
<H4>Subscribe a replication set</H4>
<BR>
<center><img src="images/slony-subscription.png"></center>
pgadmin-hackers by date: