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

13 lines
482 B
Text
Raw Normal View History

Changes 2.2.0: * Shared Libraries are now named so as to allow having multiple versions of Slony installed simultaneously on a database cluster * Let DDL for EXECUTE SCRIPT to be specified inline * Added a RESUBSCRIBE NODE command to reshape clusters. * The FAILOVER process has been reworked to be more reliable. * Major "protocol" change; rather than constructing cursors to query logged updates, version 2.2 now uses the COPY protocol to stream data into log tables on subscribers.
2013-09-11 08:45:47 +02:00
@comment $NetBSD: PLIST,v 1.6 2013/09/11 06:45:47 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
bin/slon
bin/slonik
Changes 1.2.12: - Fixed problem with DDL SCRIPT parser where C-style comments were not being processed properly - Added stored functions and documentation for adding empty tables (notably *partitions*) to replication. Note these functions do no work when not specifically requested. - Added a fairly substantial partitioning test to exercise the new stored functions above. - Backport "listen path" generator function from CVS HEAD (2.0) to 1.2 branch. - Fixed a problem with "EXECUTE SCRIPT" (introduced in remote_worker.c version 1.124.2.13) where moving the relevant code into a subroutine at the end led to losing the "BEGIN; SET TRANSACTION ISOLATION LEVEL SERIALIZABLE;" query that needs to be the first thing run... - Fixing the archive sequence generations (in log shipping). All non-SYNC events must start the local transaction before creating the archive as well, so that the lock on the archive counter table serializes archive creation. - Fixed logging done in local_listener.c - various places, there was no '\n' in some cases, which would lead to entries being folded together. - Fix launch_slons.sh - was not stripping quotes from PID file name - Error handling for "ERROR: could not serialize access due to concurrent update" - Fixes to slonik_build_env script - it wasn't properly handling cases where there was just 1 table or 1 sequence, and had a problem with the -schema option - thanks, Bernd Helmle
2008-01-14 19:58:02 +01:00
bin/slony_logshipper
Changes 2.2.0: * Shared Libraries are now named so as to allow having multiple versions of Slony installed simultaneously on a database cluster * Let DDL for EXECUTE SCRIPT to be specified inline * Added a RESUBSCRIBE NODE command to reshape clusters. * The FAILOVER process has been reworked to be more reliable. * Major "protocol" change; rather than constructing cursors to query logged updates, version 2.2 now uses the COPY protocol to stream data into log tables on subscribers.
2013-09-11 08:45:47 +02:00
lib/postgresql/slony1_funcs.${PKGVERSION}.so
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
share/postgresql/slon.conf-sample
Changes 2.2.0: * Shared Libraries are now named so as to allow having multiple versions of Slony installed simultaneously on a database cluster * Let DDL for EXECUTE SCRIPT to be specified inline * Added a RESUBSCRIBE NODE command to reshape clusters. * The FAILOVER process has been reworked to be more reliable. * Major "protocol" change; rather than constructing cursors to query logged updates, version 2.2 now uses the COPY protocol to stream data into log tables on subscribers.
2013-09-11 08:45:47 +02:00
share/postgresql/slony1_base.${PKGVERSION}.sql
share/postgresql/slony1_base.v83.${PKGVERSION}.sql
share/postgresql/slony1_base.v84.${PKGVERSION}.sql
share/postgresql/slony1_funcs.${PKGVERSION}.sql
share/postgresql/slony1_funcs.v83.${PKGVERSION}.sql
share/postgresql/slony1_funcs.v84.${PKGVERSION}.sql
Reference in a new issue Copy permalink