On 09/12/2013 09:37 AM, Merlin Moncure wrote:
On Thu, Sep 12, 2013 at 11:21 AM, Raymond O'Donnell <rod@xxxxxx> wrote:
On 12/09/2013 17:11, Patrick Dung wrote:
By the way, for in-place major version upgrade (not dumping DB and
import again), MySQL is doing a better job in here.
http://www.postgresql.org/docs/9.3/static/pgupgrade.html
pgupgrade has nothing to do with this: that's just a tool that does in
place binary upgrades of the database (basically optimizing the
dump/reload process). The mysql team OTOH maintains a comprehensive
list (albeit somewhat disorganized) of things that need to be
considered by developers and administrators before upgrading.
Postgres has no such list and yes, kudos to the mysql team for doing
so.
To be fair, our list would be much smaller and that is likely why not a
lot of effort has been put into it.
merlin
--
Command Prompt, Inc. - http://www.commandprompt.com/ 509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
For my dreams of your image that blossoms
a rose in the deeps of my heart. - W.B. Yeats
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
