Re: Postgresql upgrade from 8.4 to latest

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-29 19:33:55
Message-ID: CAGoODpdiOwYho+cyRJ8pgBo5p48kZ2zKwoeAz29srK-LS99=OA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks for good suggestions.

On Tue, Jul 28, 2015 at 3:13 PM, Joshua D. Drake <jd(at)commandprompt(dot)com>
wrote:

>
> On 07/28/2015 01:35 PM, AI Rumman wrote:
>
>> But what I read, in-place upgrade has smaller outage, compared to
>> dump/restore.
>>
>
> Correct, in fact if you do it with the link option, it will be very fast.
>
>
> But so many articles on having bugs afterwards.
>> Do you think it is a good idea to use pg_upgrade for critical database
>> application?
>>
>
> It entirely depends, I have successfully used pg_upgrade many, many times.
> That is what -c is for, to work out all the kinks before you upgrade.
>
> Or any other tool should I consider? For example - slony?
>>
>
> On at 2.5TB database, you very well be doing a lot more harm than good
> using a tool such as slony.
>
> JD
>
>
> --
> 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.
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Kevin Grittner 2015-07-29 21:10:47 Re: Synchronous replication and read consistency
Previous Message Chris Mair 2015-07-29 19:19:55 Re: Synchronous replication and read consistency