Re: Major upgrade of PostgreSQL and MySQL - Mailing list pgsql-general

From Scott Marlowe
Subject Re: Major upgrade of PostgreSQL and MySQL
Date
Msg-id CAOR=d=2N3B-z9vTRfJ6BM26AOJfS779i7CfeLhUOgKepCfabOg@mail.gmail.com
Whole thread Raw
In response to Re: Major upgrade of PostgreSQL and MySQL  (Stephen Frost <sfrost@snowman.net>)
List pgsql-general
On Fri, Sep 13, 2013 at 11:13 AM, Stephen Frost <sfrost@snowman.net> wrote:
> Patrick,
>
>
> On Friday, September 13, 2013, Patrick Dung wrote:
>>
>> >What?  That's absolutely *not* required for pg_upgrade to work.  In
>> >general, I would recommend that you make a copy of the database, but
>> >it's certainly not required.
>>
>> I mean the old version and new version would need to take up disk space on
>> the server.
>> Thus roughly doubled the disk space used.
>
>
> And I'm telling you that pg_upgrade does NOT require that. It has a mode
> which allows an in-place upgrade (using hard links) that only requires a bit
> of extra disk space- certainly no where near double on a database of any
> size.

Yeah that was one of the major reasons FOR pg upgrade was that it
could upgrade in place and not require a complete copy of the db.


pgsql-general by date:

Previous
From: Patrick Dung
Date:
Subject: Re: Major upgrade of PostgreSQL and MySQL
Next
From: Igor Neyman
Date:
Subject: Re: Major upgrade of PostgreSQL and MySQL