From: | Patrick Dung <patrick_dkt(at)yahoo(dot)com(dot)hk> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Cc: | 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:04:32 |
Message-ID: | 1379091872.8613.YahooMailNeo@web193506.mail.sg3.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
________________________________
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>
Sent: Saturday, September 14, 2013 12:43 AM
Subject: Re: [GENERAL] Major upgrade of PostgreSQL and MySQL
* Patrick Dung (patrick_dkt(at)yahoo(dot)com(dot)hk) wrote:
>> The problem of pg_upgrade is that it needed to hold two set of databases data in the server.
>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.
Thanks,
Patrick
From | Date | Subject | |
---|---|---|---|
Next Message | Patrick Dung | 2013-09-13 17:08:37 | Re: Major upgrade of PostgreSQL and MySQL |
Previous Message | Jay Vee | 2013-09-13 16:57:07 | trigger or logging |