* Scott Marlowe <scott.marlowe@gmail.com> [2008-10-06 18:07:39 CEST]:
> On Mon, Oct 6, 2008 at 9:34 AM, Markus Wanner <markus@bluegap.ch> wrote:
> > Well, it's a general Postgres problem, not a Debian one. Upgrading
> > between major versions requires a full dump/restore cycle, for which the
> > downtime is proportional to the database size. For small or medium
> > databases that's not an issue, but above some Gigabytes, that begins to
> > hurt pretty badly.
>
> In that case I prefer to have both db versions available and use slony
> to upgrade in place. We recently upgraded from 8.1 to 8.3 and work
> the downtime was measured in seconds (the time it took slony to switch
> the two servers).
Good to hear. Though I see another problem here, slony is always only
available for a single postgres version in the current packaging, so
that upgrading path isn't that easy as you make it sound... At least not
if you want to do it on a single system and not through two different
machines.
So long. :)
Rhonda