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

From Patrick Dung
Subject Re: Major upgrade of PostgreSQL and MySQL
Date
Msg-id 1379092117.12504.YahooMailNeo@web193506.mail.sg3.yahoo.com
Whole thread Raw
In response to Re: Major upgrade of PostgreSQL and MySQL  (Thomas Kellerer <spam_eater@gmx.net>)
List pgsql-general


From: Thomas Kellerer <spam_eater@gmx.net>
To: pgsql-general@postgresql.org
Sent: Saturday, September 14, 2013 12:27 AM
Subject: Re: [GENERAL] Major upgrade of PostgreSQL and MySQL

Patrick Dung wrote on 13.09.2013 18:17:
>> The problem of pg_upgrade is that it needed to hold two set of databases data in the server.
>> This is not be desirable (very slow) or possible (space limitation) for database with huge data.
>>
>> For example, if the old version is already using over 50% of the mount point.
>> The new database may not have enough disk space for the upgrading.

> I think if you use the --link parameter, you don't need additional disk space (or only little).

Thanks for pointing out.

For small or medium sized database, I think file based snapshot (like ZFS) could create backup of the old database quickly.
Also it can rollback quickly.

Thanks,
Patrick

pgsql-general by date:

Previous
From: Patrick Dung
Date:
Subject: Re: Major upgrade of PostgreSQL and MySQL
Next
From: Stephen Frost
Date:
Subject: Re: Major upgrade of PostgreSQL and MySQL