On Wed, Oct 12, 2005 at 06:15:36PM -0400, Robert Treat wrote:
IIRC Slony wont run on anything 7.3.6, so you would have to do an in place
upgrade to 7.3.x as appropriate, and then you could set up slony to propogate
to the 8.x system.
You should do that anyway, because on older releases,
On Tuesday 11 October 2005 14:59, Scott Marlowe wrote:
On Tue, 2005-10-11 at 10:50, Gary Horton wrote:
I'm needing to convince my boss that we should upgrade from 7.3.4 to
8.x Postgresql. I've already enumerated the upsides, but now we need
to consider the risks...I wonder if anyone can
I'm needing to convince my
boss that we should upgrade from 7.3.4 to 8.x Postgresql. I've already
enumerated the upsides, but now we need to consider the risks...I
wonder if anyone can mention/summarize any issues, problems, gotchas,
etc. that have happened in anyone's upgrade from 7.x to 8.x
Hi,
I did a bunch of updates from databases that where on 7.4 and there were
no issues at all.
You could always setup a test server on win32,linux or whatever and
simply restore one of your databases and see how it goes.
Tony Caduto
AM Software Design
Home of PG Lightning Admin for
On Tue, 2005-10-11 at 10:50, Gary Horton wrote:
I'm needing to convince my boss that we should upgrade from 7.3.4 to
8.x Postgresql. I've already enumerated the upsides, but now we need
to consider the risks...I wonder if anyone can mention/summarize any
issues, problems, gotchas, etc. that
Gary Horton wrote:
I'm needing to convince my boss that we should upgrade from 7.3.4 to 8.x
Postgresql. I've already enumerated the upsides, but now we need to
consider the risks...I wonder if anyone can mention/summarize any
issues, problems, gotchas, etc. that have happened in anyone's
On Oct 11, 2005, at 3:07 PM, Florian G. Pflug wrote:
On the whole, the update as quite easy ride, but I'd still
recommend you to test all aspects
of your software after the migration, since 8.0 isn't bug-for-bug
compatible with 7.4
I'll second this. One thing we found out too, was we
