Slony-I is enterprise-level "master to multiple slaves"
replication system with cascading and failover.
The big picture for the development of Slony-I is to build
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 developed as a system for data centers and backup
sites, where the normal mode of operation is that all nodes
are available.
Differences from 1.2 stream
- Removal of TABLE ADD KEY
- It drops all support for databases prior to PostgreSQL version 8.3.
===> The following configuration options are available for slony1v2-2.2.11:
DOCS=on: Build and/or install documentation
PERLTOOLS=off: Install perl configuration tools
===> Use 'make config' to modify these settings
Please read the docs on configuring and running slony-1.
Unless you did not specify the DOCS options, they are in the
/usr/local/share/doc/slony1v2 directory.
The script /usr/local/sbin/slon-mkservice can be used to create a control
directory to run and monitor the slon daemon under svscan from daemontools.
If you use this, be sure not to set slon_enable="YES" in /etc/rc.conf.
If you prefer to use the standard startup script in /usr/local/etc/rc.d then
set slon_enable="YES" in /etc/rc.conf to enable the slon.sh script.
To use either of the above startup configurations, you will need to set up a
/usr/local/etc/slon.conf file to tell slon what to replicate. This file
is documented in /usr/local/share/doc/slony1/adminguide/runtime-config.html
If upgrading
If you are upgrading from a prior version of slony, please read the UPGRADING
file in the above docs directory.
databases/slony1v2: limit to pgsql < 16
Maintainer mentions:
"PostgreSQL has grown these features internally and therefore the
upstream isn't maintained for newer postgresql."
PR: 279194
Approved by: dgilbert@eicat.ca
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
databases/slony1v2: update to 2.2.10
2.2.9 and 2.2.10 feature fixes for the new -fno-common default in GCC 10
and LLVM 11, along with some fixes for PG11+.
Approved by: dgilbert@eicat.ca (maintainer, "do it if it just compiles")
Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
Update databases/slony1v2 to version 2.2.7.
- Pass maintainership to submitter
- Sadly, man pages are no longer provided upstream
PR: 238673
Submitted by: dgilbert@eicat.ca
Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
databases/slony1v2: port cleanup
- Use OPTIONS helpers for the PERLTOOLS option
- Remove a redundant block of code for setting PGSQL_VER: this
functionality is already supplied via 'USES+= pgsql'
- Maintainer's timeout (olgeni@FreeBSD.org)
PR: 185906
Submitted by: Matthew Seaman <matthew@FreeBSD.org>
Convert USE_BISON to USES= bison
It brings bison as a build dependency in case it is set the following way:
USES= bison or USES= bison:build
it brings bison as a run dependency in case it is set the following way:
USES= bison:run
it brings bison both as a run and build dependency in case it the set the
following way:
USES= bison:both
While here trim some headers
Convert some USE_GNOME= gnomehack to USES= pathfix
In the rc.d scripts, change assignments to rcvar to use the
literal name_enable wherever possible, and ${name}_enable
when it's not, to prepare for the demise of set_rcvar().
In cases where I had to hand-edit unusual instances also
modify formatting slightly to be more uniform (and in
some cases, correct). This includes adding some $FreeBSD$
tags, and most importantly moving rcvar= to right after
name= so it's clear that one is derived from the other.
Remove painful examples of foo="", with particular prejudice against
constructions that parse out to [ -z "$foo" ] && foo=""
These are bad examples that get copied and pasted into new code, so the
hope is that with less bad examples there will be less need for me to
bring this up in review.
In a few of these files all that were changed were comments so that next
time I search for these patterns I won't trip on the file for no reason.
In a few places, add $FreeBSD$
No functional changes, so no PORTREVISION bumps
Upgrade to slony1 version 2.0.2 after repocopy.
From the slony1 home page:
"This is a major new release of Slony-I; it makes use of some
features introduced in PostgreSQL 8.3, and hence is not compatible
with versions older than 8.3. This is considered a pretty good
tradeoff, as various functionality would not be possible with earlier
versions of PostgreSQL."
Support for PostgreSQL 8.4 will be available in slony1 2.0.3, hence
IGNORE_WITH_PGSQL also contains 84 for now.
This port conflicts with slony1-*.
PR: ports/135096 (with a few changes)
Submitted by: Ismail Yenigul <ismail.yenigul at endersys.com.tr>
Repocopy by: marcus
