Slony1 PostgreSQL Replication - Slony-I 1.1 Release Candidate #1 Now Available

Author

Slony-I 1.1 Release Candidate #1 Now Available

Christopher Browne

2005-06-10, 8:24 pm

After much testing and fending off bugs, we now have a release
candidate available. It has been tested out on quite a number of
platforms, and numerous bugs have been "stomped out."

There are a great deal of changes since version 1.0.5, including:

o Greatly extended documentation
o Logging includes date stamps
o Slonik now supports define/include (similar to CPP)
o Automatic generation of "Listen Paths" (formerly an error-prone manual process)
o slon daemons are greatly more configurable and can use config files
o Log shipping allows creating offline replicas
o Numerous improvements to automated maintenance
o Build environment no longer requires a full PostgreSQL source tree
This enormously eases the use of Slony-I on systems using prepackaged binaries.
o Numerous bug fixes

You can find a copy of the "Admin Guide" documentation online here:
<http://developer.postgresql.org/~wi...nguide-1.1.rc1/>

The tarball is available here:
<http://developer.postgresql.org/~wi...1.0.rc1.tar.bz2>

The general idea at this point is to encourage people to run this in
as many places as possible so as to find any lingering problems.

Testing has already taken place on numerous platforms, including:
- Debian/Linux/IA-32
- Red Hat Fedora Core 2
- Red Hat RHAS 3
- OpenBSD/SPARC
- Solaris/SPARC
- AIX/PPC
- FreeBSD/IA-32

There are enough variations between those platforms in terms of word
sizes, endianness, and flavours of Unix to build some confidence; we
hope for a 1.1 full release soon.
--
"cbbrowne","@","ca.afilias.info"
Christopher Browne
(416) 673-4124 (land)

elein

2005-06-10, 8:24 pm

There are problems with the slon start & kill scripts
on RH9. The watchdog keeps giving error messages about
bad dashes and pointing the user to faq for procps.

Then when you try to slon_kill it only succeeds in
killing the watchdog because it errors out on the
dash errors. You have to run it twice before killing
off the slon processes.

--elein
elein- JkRegAVoul5BDgjK7y7T
UQ@public.gmane.org

On Fri, Jun 10, 2005 at 03:45:09PM -0400, Christopher Browne wrote:
> After much testing and fending off bugs, we now have a release
> candidate available. It has been tested out on quite a number of
> platforms, and numerous bugs have been "stomped out."
>
> There are a great deal of changes since version 1.0.5, including:
>
> o Greatly extended documentation
> o Logging includes date stamps
> o Slonik now supports define/include (similar to CPP)
> o Automatic generation of "Listen Paths" (formerly an error-prone manual process)
> o slon daemons are greatly more configurable and can use config files
> o Log shipping allows creating offline replicas
> o Numerous improvements to automated maintenance
> o Build environment no longer requires a full PostgreSQL source tree
> This enormously eases the use of Slony-I on systems using prepackaged binaries.
> o Numerous bug fixes
>
> You can find a copy of the "Admin Guide" documentation online here:
> <http://developer.postgresql.org/~wi...nguide-1.1.rc1/>
>
> The tarball is available here:
> <http://developer.postgresql.org/~wi...1.0.rc1.tar.bz2>
>
> The general idea at this point is to encourage people to run this in
> as many places as possible so as to find any lingering problems.
>
> Testing has already taken place on numerous platforms, including:
> - Debian/Linux/IA-32
> - Red Hat Fedora Core 2
> - Red Hat RHAS 3
> - OpenBSD/SPARC
> - Solaris/SPARC
> - AIX/PPC
> - FreeBSD/IA-32
>
> There are enough variations between those platforms in terms of word
> sizes, endianness, and flavours of Unix to build some confidence; we
> hope for a 1.1 full release soon.
> --
> "cbbrowne","@","ca.afilias.info"
> Christopher Browne
> (416) 673-4124 (land)
> ____________________
____________________
_______
> Slony1-general mailing list
> Slony1-general- AuKwsB3Fm+ugFIWk8tvy
RWD2FQJk+8+b@public.gmane.org
> http://gborg.postgresql.org/mailman.../slony1-general
>

Hannu Krosing

2005-06-11, 3:29 am

On R, 2005-06-10 at 15:45 -0400, Christopher Browne wrote:
> After much testing and fending off bugs, we now have a release
> candidate available. It has been tested out on quite a number of
> platforms, and numerous bugs have been "stomped out."

form the docs:

<doc>
You may apply triggers on the "disconnected node " to do additional
processing on the data

For instance, you might take a fairly "stateful" database and turn it
into a "temporal" one by use of triggers that implement the techniques
described in [Developing Time-Oriented Database Applications in SQL ] by
Richard T. Snodgrass.
</doc>

Another cool use is in data warehousing and OLAP applications where the
shipped logs, together with rules/triggers can be used to create all
kinds of materialized views.

--
Hannu Krosing <hannu-7C/ iILuz2RdeoWH0uzbU5w@
public.gmane.org>

cbbrowne-swQf4SbcV9C7WVzo/KQ3Mw@public.gmane.org

2005-06-12, 8:24 pm

> There are problems with the slon start & kill scripts
> on RH9. The watchdog keeps giving error messages about
> bad dashes and pointing the user to faq for procps.
>
> Then when you try to slon_kill it only succeeds in
> killing the watchdog because it errors out on the
> dash errors. You have to run it twice before killing
> off the slon processes.

Oh, dear.

There are evidently some variations between differing Linux
implementations as to how they cope with ps flags.

I think we have enough flavours of Linux around the office to be able to
check for different behaviours. Red Hat, Debian, and SuSE should cover a
goodly number of bases.

I'll have to take a look tomorrow.

Sponsored Links