| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Installing/Upgrading PostgreSQL 9.1.6 to 9.3 known bugs? |
| Date: | 2013-10-02 14:29:21 |
| Message-ID: | 20131002142921.GE21547@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Sep 20, 2013 at 02:00:05PM -0700, John R Pierce wrote:
> On 9/20/2013 1:51 PM, fburgess(at)radiantblue(dot)com wrote:
>
> 1.) During our prior upgrade process we used pg_upgrade to move from pg
> 8.4.3 to 9.1.6 using the hard links install option, we also have our data
> spread across disk storage mediums; fiber, nas. Are there any known issues,
> bugs with using pg_upgrade to move from 9.1.6 to pg 9.3?
>
>
>
> having multiple tablespaces on different mount points complicates things. I'm
> not sure how or if pg_upgrade handles that.
pg_upgrade is fine with that. The old/new tablespaces stay in the same
mount point as just per-version subdirectories.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2013-10-02 16:00:44 | Re: BUG #8467: Slightly confusing pgcrypto example in docs |
| Previous Message | Bruce Momjian | 2013-10-02 14:15:13 | Re: psql \i command with a missing file name doesn't rollback the transaction |