From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Patrick Dung <patrick_dkt(at)yahoo(dot)com(dot)hk> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, Ivan Voras <ivoras(at)freebsd(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net> |
Subject: | Re: Major upgrade of PostgreSQL and MySQL |
Date: | 2013-09-13 17:13:44 |
Message-ID: | CAOuzzgovj5g9ex9NcD1BCWQW2OU67Hfv_7GkxNR-EV4xqiiR=Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Andrus | 2013-09-13 17:22:11 | The signature of postgresql-9.3.0-1-windows.exe is corrupt or invalid |
Previous Message | Patrick Dung | 2013-09-13 17:08:37 | Re: Major upgrade of PostgreSQL and MySQL |