ading PostgreSQL 9.1.6 to 9.3 known
bugs?
From: Bruce Momjian <br...@momjian.us>
Date: Tue, October 08, 2013 6:17 am
To: fburg...@radiantblue.com
Cc: pgsql-bugs@postgresql.org
On Mon, Oct 7, 2013 at 08:07:42AM -0700, fburg...@radiantblue.com wrote:
> Bruce, Proposed Steps. Do they look fe
On Mon, Oct 7, 2013 at 08:07:42AM -0700, fburg...@radiantblue.com wrote:
> 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-p
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 <br...@momjian.us>
Date:
On Fri, Sep 20, 2013 at 02:00:05PM -0700, John R Pierce wrote:
> On 9/20/2013 1:51 PM, fburg...@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
On 9/20/2013 1:51 PM, fburg...@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_
