Re: upgrading from 9.3-beta1 to 9.3-beta2 requires dump & reload?

From: Lonni J Friedman <netllama(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, maintainers(at)lists(dot)pgrpms(dot)org, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: upgrading from 9.3-beta1 to 9.3-beta2 requires dump & reload?
Date: 2013-07-24 21:52:43
Message-ID: CAP=oouGANz-02nPf-ZK_6EShyBUjELWJJV-EjjDUA=FKJ8cX2w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Jul 24, 2013 at 2:05 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
>> Lonni J Friedman escribió:
>>> I'm using the RPMs from yum.postgresql.org on RHEL6. Is this
>>> expected, intentional behavior? Do I really need to dump & reload to
>>> upgrade between beta releases of 9.3, or is there some more efficient
>>> way?
>
>> We try to avoid forcing initdb between beta versions, but it's not
>> guaranteed. You should be able to use pg_upgrade, also.
>
> Unfortunately, the RPMs probably won't be very helpful for using
> pg_upgrade, since there's no convenient way to get beta1 and beta2
> postmaster executables installed at the same time (unless Devrim
> foresaw this case and packaged things differently than I did for
> Red Hat ;-)).

Sounds like I'm out of luck. Thanks anyway.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message John R Pierce 2013-07-24 23:26:37 Re: Tablespace on Postgrsql
Previous Message Sergey Konoplev 2013-07-24 21:11:03 Re: unique index corruption