From: | AI Rumman <rummandba(at)gmail(dot)com> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | pgsql-general General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Postgresql upgrade from 8.4 to latest |
Date: | 2015-07-28 20:35:08 |
Message-ID: | CAGoODpcrt6OpZhGzti33e8zygwMX7ueWafUTi6hrUU1+cYPQiQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
But what I read, in-place upgrade has smaller outage, compared to
dump/restore. But so many articles on having bugs afterwards.
Do you think it is a good idea to use pg_upgrade for critical database
application?
Or any other tool should I consider? For example - slony?
Thanks for advice.
Regards.
On Tue, Jul 28, 2015 at 1:29 PM, Joshua D. Drake <jd(at)commandprompt(dot)com>
wrote:
>
> On 07/28/2015 01:12 PM, AI Rumman wrote:
>
>> Hi,
>>
>> I need to upgrade Postgresql database from 8.4 to latest stable version
>> (9.4). The db size is almost 2.5 TB.
>> Is pg_upgrade in-place is a good idea for it?
>>
>
> With quite a bit of testing, yes.
>
> But keep in mind, it is still an outage.
>
> JD
>
>
>
>> Thanks for advice.
>>
>> Regards.
>>
>
>
> --
> Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
> PostgreSQL Centered full stack support, consulting and development.
> Announcing "I'm offended" is basically telling the world you can't
> control your own emotions, so everyone else should do it for you.
>
From | Date | Subject | |
---|---|---|---|
Next Message | John R Pierce | 2015-07-28 20:35:16 | Re: Postgresql upgrade from 8.4 to latest |
Previous Message | Joshua D. Drake | 2015-07-28 20:29:17 | Re: Postgresql upgrade from 8.4 to latest |