Tue Jan 30 11:57:29 PST 2007
- Previous message: [Slony1-commit] slony1-engine/doc/adminguide adminscripts.sgml
- Next message: [Slony1-commit] slony1-www index.php
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Update of /home/cvsd/slony1/slony1-www/content In directory main:/tmp/cvs-serv23196 Added Files: frontpage.txt Log Message: Extra info for frontpage. --- NEW FILE: frontpage.txt --- Slony-I 1.2.6 # <p>At long last, here is version 1.2.6. It has many enhancements as listed in the <a href= "http://pgfoundry.org/frs/shownotes.php?release_id=730">Release Notes</a> .</p> <p>This has been run thru the <a href= "http://linuxdatabases.info/info/releasechecklist.html">Release Checklist</a></p> <p>There are two tarballs available <a href= "http://pgfoundry.org/frs/?group_id=1000122">here</a></p> --- Slony-I and PostgreSQL 8.1 # <p>There is a known incompatibility of versions earlier than 1.1.5 with version 8.1; you can expect to see the following error message when compiling:</p> <pre> slony1_funcs.c:1081: error: too many arguments to function `Async_Unlisten' </pre> <p>A patch for both version 1.1 "STABLE" and CVS HEAD has been committed to CVS; look at both CVS HEAD as well as <tt>REL_1_1_STABLE</tt>. It is in the 1.1.5 release candidate described above.</p> --- Upgrading Slony-I # <p>Beginning with version 1.0.5 the slon replication engine refuses to work against any database that does not have the stored procedures for the same version loaded or where the shared object containing the C language support functions and the log trigger does not match the version number.</p> <p>This means that the Slony installation on all nodes in a cluster must be upgraded at once.</p> <p>The proper upgrade procedure is this:</p> <ol> <li>Stop the slon replication engine on all nodes.</li> <li>Install the new Slony version on all nodes.</li> <li>Execute a slonik script containing the command <pre> update functions (id = ); </pre>for every node in the cluster. </li> <li>Start all slon replication engines.</li> </ol> <p>For more details, see also <a href= "./adminguide/slony1-1.2.6/doc/adminguide/slonyupgrade.html"> Upgrading Slony-I</a> .</p> --- Libpq requirements # <p>The multithreaded replication engine requires the libpq client library to be compiled with --enable-thread-safety on certain operating systems. Known are thus far Solaris and AIX. Other operating systems are known to not require this (Linux-X86, FreeBSD-X86, FreeBSD-Alpha, OpenBSD-Sparc64 and OSX). The configuration script is broken with respect to the --enable-thread-safety switch for Solaris. Please apply this patch, configure and recompile libpq: <a href= "http://developer.postgresql.org/%7Ewieck/slony1/download/threadsafe-libpq-742.diff.gz"> threadsafe-libpq-742.diff.gz.</a></p> --- RPMs http://pgfoundry.org/projects/slony1 <p>RPM files for some versions of Red Hat Linux are available <a href= "http://pgfoundry.org/projects/slony1">here</a> , including SRPM (Source RPM) files that may be helpful if you wish to generate RPM files for distributions not yet supported.</p> <p>This project is released under the Berkeley/BSD license.</p>
- Previous message: [Slony1-commit] slony1-engine/doc/adminguide adminscripts.sgml
- Next message: [Slony1-commit] slony1-www index.php
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list