Thu Sep 18 14:30:11 PDT 2008
- Previous message: [Slony1-commit] slony1-engine/doc/adminguide loganalysis.sgml
- Next message: [Slony1-commit] slony1-engine/tests run_test.sh
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Update of /home/cvsd/slony1/slony1-engine/doc/adminguide In directory main.slony.info:/tmp/cvs-serv6868 Modified Files: firstdb.sgml Log Message: Note change in post-8.0 PG releases regarding TCP/IP sockets Index: firstdb.sgml =================================================================== RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/firstdb.sgml,v retrieving revision 1.28 retrieving revision 1.29 diff -C2 -d -r1.28 -r1.29 *** firstdb.sgml 12 May 2008 15:10:28 -0000 1.28 --- firstdb.sgml 18 Sep 2008 21:30:08 -0000 1.29 *************** *** 31,35 **** <listitem><para> You have <option>tcpip_socket=true</option> in your ! <filename>postgresql.conf</filename> and</para></listitem> <listitem><para> You have enabled access in your cluster(s) via --- 31,35 ---- <listitem><para> You have <option>tcpip_socket=true</option> in your ! <filename>postgresql.conf</filename>;</para> <note> <para> This is no longer needed for &postgres; 8.0 and later versions.</para></note> </listitem> <listitem><para> You have enabled access in your cluster(s) via *************** *** 160,163 **** --- 160,181 ---- procedures in the master/slave (node) databases. </para> + <para> The example that follows uses <xref linkend="slonik"> directly + (or embedded directly into scripts). This is not necessarily the most + pleasant way to get started; there exist tools for building <xref + linkend="slonik"> scripts under the <filename>tools</filename> + directory, including:</para> + <itemizedlist> + <listitem><para> <xref linkend="altperl"> - a set of Perl scripts that + build <xref linkend="slonik"> scripts based on a single + <filename>slon_tools.conf</filename> file. </para> </listitem> + + <listitem><para> <xref linkend="mkslonconf"> - a shell script + (<emphasis>e.g.</emphasis> - works with Bash) which, based either on + self-contained configuration or on shell environment variables, + generates a set of <xref linkend="slonik"> scripts to configure a + whole cluster. </para> </listitem> + + </itemizedlist> + <sect3><title>Using slonik command directly</title>
- Previous message: [Slony1-commit] slony1-engine/doc/adminguide loganalysis.sgml
- Next message: [Slony1-commit] slony1-engine/tests run_test.sh
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list