SVN Commit by andreas: r4596 - trunk/pgadmin3/docs/en_US - Mailing list pgadmin-hackers

From svn@pgadmin.org
Subject SVN Commit by andreas: r4596 - trunk/pgadmin3/docs/en_US
Date
Msg-id 200510231548.j9NFm6Dg020073@developer.pgadmin.org
Whole thread Raw
List pgadmin-hackers
Author: andreas
Date: 2005-10-23 16:48:06 +0100 (Sun, 23 Oct 2005)
New Revision: 4596

Modified:
   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:
adding hooks

Modified: trunk/pgadmin3/docs/en_US/slony-install.html
===================================================================
--- trunk/pgadmin3/docs/en_US/slony-install.html    2005-10-23 14:46:51 UTC (rev 4595)
+++ trunk/pgadmin3/docs/en_US/slony-install.html    2005-10-23 15:48:06 UTC (rev 4596)
@@ -3,11 +3,12 @@
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
 <link rel="STYLESHEET" type="text/css" href="pgadmin3.css">
-<title>Slony-I administration with pgAdmin III: overview</title>
+<title>Slony-I administration with pgAdmin III: installation</title>
 </head>

 <body>
-<h3>Slony-I administration with pgAdmin III: overview</h3>
+<A name='node'/>
+<h3>Slony-I administration with pgAdmin III: installation</h3>
 <BR>
 <H4>Prerequisites</H4>
 <p>
@@ -17,7 +18,10 @@
 a PostgreSQL 8.1 server on Win32, the windows installer routine can do this
 for you if you select the "Slony-I" installation option.
 </p>
-<BR><BR>
+<BR><BR><BR>
+<A name='create'/>
+<H4>Create cluster and first node</H4>
+<BR>
 <center><img src="images/slony-create.png"></center>

 <p>
@@ -30,6 +34,10 @@
 To achieve this, pgAdmin III uses the concept of "Administrative nodes".

 </p>
+<BR><BR><BR>
+<A name='join'/>
+<H4>Join additional nodes to cluster</H4>
+<BR>
 <center><img src="images/slony-join.png"></center>
 <p>
 After the first node in the Slony-I replication cluster has been successfully created,
@@ -42,6 +50,10 @@
 <A href='"slony-path.html'>replication paths</A> between the nodes, to enable communication
 between the nodes.
 </p>
+<BR><BR><BR>
+<A name='upgrade'/>
+<H4>Upgrade node to new cluster software</H4>
+<BR>
 <center><img src="images/slony-upgrade.png"></center>
 <p>
 When a cluster is to be upgraded to a new version of the Slony-I clustering software,

Modified: trunk/pgadmin3/docs/en_US/slony-path.html
===================================================================
--- trunk/pgadmin3/docs/en_US/slony-path.html    2005-10-23 14:46:51 UTC (rev 4595)
+++ trunk/pgadmin3/docs/en_US/slony-path.html    2005-10-23 15:48:06 UTC (rev 4596)
@@ -8,9 +8,11 @@

 <body>
 <h3>Creating paths and listens</h3>
-
+<BR><BR><BR>
+<A name='path'/>
+<H4>Create paths to other nodes</H4>
+<BR>
 <center><img src="images/slony-path.png"></center>
-
 <p>
 Slony-I needs path information, that defines how a slon process can communicate to
 other nodes. The conninfo string takes a connect string as described in the
@@ -18,6 +20,9 @@
 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'/>
+<H4>Create listens to other nodes</H4>
 <BR>
 <center><img src="images/slony-listen.png"></center>
 <p>

Modified: trunk/pgadmin3/docs/en_US/slony-set.html
===================================================================
--- trunk/pgadmin3/docs/en_US/slony-set.html    2005-10-23 14:46:51 UTC (rev 4595)
+++ trunk/pgadmin3/docs/en_US/slony-set.html    2005-10-23 15:48:06 UTC (rev 4596)
@@ -9,12 +9,18 @@
 <body>
 <h3>Creating sets and subscriptions</h3>

+<BR><BR><BR>
+<A name='set'/>
+<H4>Create replication set</H4>
+<BR>
 <center><img src="images/slony-set.png"></center>
-
 <p>
 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'/>
+<H4>Define replicated table</H4>
 <BR>
 <center><img src="images/slony-table.png"></center>
 <p>
@@ -34,11 +40,17 @@
 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'/>
+<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'/>
+<H4>Subscribe a replication set</H4>
 <BR>
 <center><img src="images/slony-subscription.png"></center>
 <p>


pgadmin-hackers by date:

Previous
From: svn@pgadmin.org
Date:
Subject: SVN Commit by andreas: r4595 - trunk/pgadmin3/docs/en_US
Next
From: svn@pgadmin.org
Date:
Subject: SVN Commit by andreas: r4597 - in trunk/pgadmin3/src: dlg slony slony/include