kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/databases/slony1/distinfo

8 lines
362 B
Text
Raw Normal View History

Changes 2.0.6: -Fix: Removing extranous '//' from the perl script. -Fix: slon can segfault while shutting down. -Fix: typenameTypeId() changes signatures in 9.1 -Fix: if slon gets confused waiting for its child it will exit. -Fix: distclean deletes the slony_logshipper flex/bison generated files.
2010-12-14 18:57:24 +01:00
$NetBSD: distinfo,v 1.12 2010/12/14 17:57:24 adam Exp $
Slony-I is a "master to multiple slaves" replication system with cascading and failover. The big picture for the development of Slony-I is a master-slave system that includes all features and capabilities needed to replicate large databases to a reasonably limited number of slave systems. Slony-I is a system for data centers and backup sites, where the normal mode of operation is that all nodes are available
2006-06-02 17:05:16 +02:00
Changes 2.0.6: -Fix: Removing extranous '//' from the perl script. -Fix: slon can segfault while shutting down. -Fix: typenameTypeId() changes signatures in 9.1 -Fix: if slon gets confused waiting for its child it will exit. -Fix: distclean deletes the slony_logshipper flex/bison generated files.
2010-12-14 18:57:24 +01:00
SHA1 (slony1-2.0.6.tar.bz2) = 6e3c8d9bb8ae138c089782836f9b303cadc82b97
RMD160 (slony1-2.0.6.tar.bz2) = 39ceec9fc823903e6e2c6080558ab5e00a476697
Size (slony1-2.0.6.tar.bz2) = 979208 bytes
Changes 2.0.2: * PostgreSQL 8.4 compatibility * Fix - config dump was failing on string entries that were NULL * Fix - REPAIR CONFIG could have collisions where, when we load a schema, one entry in sl_table already has an OID value that incorrectly matches a value that another update is trying to fix. * Updated release notes to indicate that 2.0 only supports PostgreSQL 8.3+ * Change to configure.ac to allow it to run on autoconf 2.63; there was something unsuitable about SLONREL_VERSION processing * Fixes to Makefile for admin guide * Various fixes to admin guide material * Added an extra test to Schema name test that validates that things can operate properly even if the DB lacks a "public" schema * Fixed bug in tools/start_slon.sh * Fixed pathname substitutions in a couple of altperl scripts * Add a test which validates that the cluster schema name is valid; pgAdminIII allowed setting up cluster names that slonik would refuse to connect to. * Revised regression tests to use SYNC/WAIT FOR EVENT instead of queries that try to coordinate sl_status information with rather less determinacy... * Cleanup thread was generating spurious error messages due to misinterpreting PG return codes. Rectified this, and added a test in to make sure we're exercising the logic
2010-04-15 09:55:31 +02:00
SHA1 (patch-aa) = 591635aa8badd2690629ffd4ba1d4a619d332fbc
SHA1 (patch-ab) = de4549aa7fae7aed10f4ebb14de8d5aea5419cb4
Reference in a new issue Copy permalink