On 13.04.2013 12:35, Adam D. Barratt wrote:
On Wed, 2013-03-20 at 16:49 -0400, Peter Eisentraut wrote:
On 3/19/13 2:48 PM, Steve Singer wrote:
Since the original bug was opened we've figured out why adding PG
9.1
support to slony 2.0.x was causing occasional test failures.
The fixes for
On Wed, 2013-03-20 at 16:49 -0400, Peter Eisentraut wrote:
On 3/19/13 2:48 PM, Steve Singer wrote:
Since the original bug was opened we've figured out why adding PG 9.1
support to slony 2.0.x was causing occasional test failures.
The fixes for PG 9.1 (upstream bugs #255) along with the
Attached are two patches that should allow Slony 2.0.7 to work with PG 9.1
I've run slony with these patches through a number of runs of the
clustertest suites and everything works as expected (lots of other bugs
fixed in 2.1 and 2.2 are still present)
Steve
From
On 3/19/13 2:48 PM, Steve Singer wrote:
Since the original bug was opened we've figured out why adding PG 9.1
support to slony 2.0.x was causing occasional test failures.
The fixes for PG 9.1 (upstream bugs #255) along with the fixes for the
MOVE SET issue caused by the #255 fix (upstream
user debian-rele...@packages.debian.org
usertags 678979 wheezy-will-remove
thanks
On Sat, Mar 16, 2013 at 12:44:15PM -0400, Peter Eisentraut wrote:
On Sat, 2013-03-16 at 11:38 +, Adam D. Barratt wrote:
On Sun, 2012-10-07 at 14:30 +0200, Mehdi Dogguy wrote:
On 21/09/2012 04:58, Peter
Since the original bug was opened we've figured out why adding PG 9.1
support to slony 2.0.x was causing occasional test failures.
The fixes for PG 9.1 (upstream bugs #255) along with the fixes for the
MOVE SET issue caused by the #255 fix (upstream bug #285) I think will
produce a working
On Sun, 2012-10-07 at 14:30 +0200, Mehdi Dogguy wrote:
On 21/09/2012 04:58, Peter Eisentraut wrote:
According to bug #678979 [0], which was submitted by the lead
upstream developer, slony 2.0 does not work well with postgresql
9.1. Therefore, we had to resolve to making an upgrade to slony
On Sat, 2013-03-16 at 11:38 +, Adam D. Barratt wrote:
On Sun, 2012-10-07 at 14:30 +0200, Mehdi Dogguy wrote:
On 21/09/2012 04:58, Peter Eisentraut wrote:
According to bug #678979 [0], which was submitted by the lead
upstream developer, slony 2.0 does not work well with postgresql
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/09/2012 04:58, Peter Eisentraut wrote:
According to bug #678979 [0], which was submitted by the lead
upstream developer, slony 2.0 does not work well with postgresql
9.1. Therefore, we had to resolve to making an upgrade to slony
version
According to bug #678979 [0], which was submitted by the lead upstream
developer, slony 2.0 does not work well with postgresql 9.1. Therefore,
we had to resolve to making an upgrade to slony version 2.1, and I
request that that be allowed into wheezy now.
To be precise: The source package name
10 matches
Mail list logo