SVN Commit by dpage: r4893 - branches/REL-1_4_0_PATCHES/pgadmin3/docs/en_US - Mailing list pgadmin-hackers
| From | svn@pgadmin.org |
|---|---|
| Subject | SVN Commit by dpage: r4893 - branches/REL-1_4_0_PATCHES/pgadmin3/docs/en_US |
| Date | |
| Msg-id | 200601121406.k0CE6rG3024112@developer.pgadmin.org Whole thread Raw |
| List | pgadmin-hackers |
Author: dpage Date: 2006-01-12 14:06:53 +0000 (Thu, 12 Jan 2006) New Revision: 4893 Modified: branches/REL-1_4_0_PATCHES/pgadmin3/docs/en_US/slony-install.html branches/REL-1_4_0_PATCHES/pgadmin3/docs/en_US/slony-path.html branches/REL-1_4_0_PATCHES/pgadmin3/docs/en_US/slony-set.html Log: Tweak HTML Modified: branches/REL-1_4_0_PATCHES/pgadmin3/docs/en_US/slony-install.html =================================================================== --- branches/REL-1_4_0_PATCHES/pgadmin3/docs/en_US/slony-install.html 2006-01-12 13:46:32 UTC (rev 4892) +++ branches/REL-1_4_0_PATCHES/pgadmin3/docs/en_US/slony-install.html 2006-01-12 14:06:53 UTC (rev 4893) @@ -16,7 +16,7 @@ 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> <H4>Create cluster and first node</H4> <BR> @@ -32,7 +32,7 @@ To achieve this, pgAdmin III uses the concept of "Administrative nodes". </p> -<BR><BR><BR> + <A name="join"></a> <H4>Join additional nodes to cluster</H4> <BR> @@ -48,7 +48,7 @@ <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> <H4>Upgrade node to new cluster software</H4> <BR> Modified: branches/REL-1_4_0_PATCHES/pgadmin3/docs/en_US/slony-path.html =================================================================== --- branches/REL-1_4_0_PATCHES/pgadmin3/docs/en_US/slony-path.html 2006-01-12 13:46:32 UTC (rev 4892) +++ branches/REL-1_4_0_PATCHES/pgadmin3/docs/en_US/slony-path.html 2006-01-12 14:06:53 UTC (rev 4893) @@ -8,8 +8,8 @@ <body> <h3>Creating paths and listens</h3> -<BR><BR><BR> -<A name='path'/> + +<A name="path"></a> <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"></a> <H4>Create listens to other nodes</H4> <BR> <center><img src="images/slony-listen.png"></center> Modified: branches/REL-1_4_0_PATCHES/pgadmin3/docs/en_US/slony-set.html =================================================================== --- branches/REL-1_4_0_PATCHES/pgadmin3/docs/en_US/slony-set.html 2006-01-12 13:46:32 UTC (rev 4892) +++ branches/REL-1_4_0_PATCHES/pgadmin3/docs/en_US/slony-set.html 2006-01-12 14:06:53 UTC (rev 4893) @@ -9,8 +9,7 @@ <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 +17,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 +39,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"> <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: