Postgres Pro
Downloads
Home   >   mailing lists

Re: Installing/Upgrading PostgreSQL 9.1.6 to 9.3 knownbugs? - Mailing list pgsql-bugs

From
Subject Re: Installing/Upgrading PostgreSQL 9.1.6 to 9.3 knownbugs?
Date
Msg-id 20131007080742.5a830134ae84016b0174832fdc1a3173.370d0aaa3c.wbe@email11.secureserver.net
Whole thread Raw
Responses Re: Installing/Upgrading PostgreSQL 9.1.6 to 9.3 known bugs?  (Bruce Momjian <bruce@momjian.us>)
List pgsql-bugs
Tree view
Bruce, Proposed Steps. Do they look feasible?

1.) pg_dump -h localhost -p 5432 -U postgres -Fc -b -v -f "/somepath/testdb.backup" testdb
2.) CREATE DATABASE newdb TEMPLATE=template_postgis;
3.) perl ../postgis-postgres/postgis-2.1.1/utils/postgis_restore.pl "/somepath/testdb.backup" | psql -h localhost -p 5432 -U postgres newdb 2> errors.txt  <- this step may run 5-6 days, since our backup runs that long, right?
4.) At this point we will have two 6.1TB databases, so it looks like a prerequisite is to have available double the db size in disk space, right?
5.) then if no critical errors, there will be errors since we have our testdb schema in the public folder
  5a.) ALTER DATABASE testdb RENAME TO olddb;
  5b.) ALTER DATABASE newdb RENAME TO testdb;
6.) At this point hopefully we should be upgraded from postgis 1.5.3 to postgis 2.1.1, with PostgreSQL 9.1.6
7.) then can we just use pg_upgrade with the hard links option, instead of copying files to the new cluster option to upgrade to PostgreSQL 9.3?

-------- Original Message --------
Subject: Re: [BUGS] Installing/Upgrading PostgreSQL 9.1.6 to 9.3 known
bugs?
From: Bruce Momjian <bruce@momjian.us>
Date: Wed, October 02, 2013 7:29 am
To: John R Pierce <pierce@hogranch.com>
Cc: pgsql-bugs@postgresql.org

On Fri, Sep 20, 2013 at 02:00:05PM -0700, John R Pierce wrote:
> On 9/20/2013 1:51 PM, fburgess@radiantblue.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@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +


--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #8470: 9.3 locking/subtransaction performance regression
Next
From: Sandeep Thakkar
Date:
Subject: Re: BUG #8493: Changing file permissions on all files during install