| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | "Raymond O'Donnell" <rod(at)iol(dot)ie> |
| Cc: | Patrick Dung <patrick_dkt(at)yahoo(dot)com(dot)hk>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Major upgrade of PostgreSQL and MySQL |
| Date: | 2013-09-12 16:37:44 |
| Message-ID: | CAHyXU0yXwKg+zwO5jLKLbmVSiE=2idSmM2UYvmsdvYMC6KKVfg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Sep 12, 2013 at 11:21 AM, Raymond O'Donnell <rod(at)iol(dot)ie> 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.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2013-09-12 16:47:39 | Re: Major upgrade of PostgreSQL and MySQL |
| Previous Message | Raymond O'Donnell | 2013-09-12 16:21:25 | Re: Major upgrade of PostgreSQL and MySQL |