public inbox for [email protected]
help / color / mirror / Atom feedFrom: Jim C. Nasby <[email protected]>
To: Tino Wildenhain <[email protected]>
To: Jeff Davis <[email protected]>
To: [email protected]
To: PgSQL General List <[email protected]>
To: [email protected]
Subject: Re: Fast major-version upgrade (was: [GENERAL] postgresql 8.0 advantages)
Date: Tue, 1 Mar 2005 13:14:26 -0600
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<1109410075.4089.216.camel@jeff>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
On Mon, Feb 28, 2005 at 09:27:46PM +0100, Martijn van Oosterhout wrote:
> On Mon, Feb 28, 2005 at 01:36:59PM -0600, Jim C. Nasby wrote:
> > > I used a straight copy of the filesystem with running database
> > > (over the net in my case) and immediately after that,
> > > stop the db and rsync for the last changes. This took only
> > > 10 minutes (compared to 1.5h for the full filesystem copy)
> > > and I could start up the db in new location.
> > >
> > > this could work for you too.
> >
> > I hadn't thought about using rsync; that's a great idea!
> >
> > Is there somewhere this could be documented? In an FAQ maybe?
>
> It works only in the special case where the PostgreSQL version number
> is the same and you're running on the same platform. How often are you
> transferring databases like that. Even transferring from i386 to amd64
> wouldn't work like this AFAIUI.
Absolutely true, although in the case of database version PostgreSQL
will check that itself. But in the context this was originally brought
up in (using Sloney to upgrade a machine from 7.4.x to 8.x), it would
work great, and rsync would make a huge difference in downtime.
--
Jim C. Nasby, Database Consultant [email protected]
Give your computer some brain candy! www.distributed.net Team #1828
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"
view thread (15+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Fast major-version upgrade (was: [GENERAL] postgresql 8.0 advantages)
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox