| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Lonni J Friedman <netllama(at)gmail(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:05:37 |
| Message-ID: | 29864.1374699937@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 ;-)).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2013-07-24 21:08:45 | Re: unique index corruption |
| Previous Message | Alvaro Herrera | 2013-07-24 20:59:23 | Re: upgrading from 9.3-beta1 to 9.3-beta2 requires dump & reload? |