<html><body><span style="font-family:Verdana; color:#000000; font-size:10pt;"><div>Bruce, Proposed Steps. Do they look feasible?<br><br>1.) pg_dump -h localhost -p 5432 -U postgres -Fc -b -v -f "/somepath/testdb.backup" testdb<br>2.) CREATE DATABASE newdb TEMPLATE=template_postgis;<br>3.) perl ../postgis-postgres/postgis-2.1.1/utils/<a href="http://postgis_restore.pl">postgis_restore.pl</a> "/somepath/testdb.backup" | psql -h localhost -p 5432 -U postgres newdb 2> errors.txt <- <b>this step may run 5-6 days, since our backup runs that long, right?</b><br>4.) At this point we will have two 6.1TB databases, <b>so it looks like a prerequisite is to have available double the db size in disk space, right?</b></div><div>5.) then if no critical errors, there will be errors since<span mce_style="color: #333333;" style="color: rgb(51, 51, 51);"> <span mce_style="line-height: 115%;" style="line-height: 115%;">we have our testdb schema in the
public folder</span></span><br> 5a.) ALTER DATABASE testdb RENAME TO olddb;<br> 5b.) ALTER DATABASE newdb RENAME TO testdb;<br>6.) At this point hopefully we should be upgraded from postgis 1.5.3 to postgis 2.1.1, with PostgreSQL 9.1.6<br>7.) <b>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? </b><br><br></div>
<blockquote id="replyBlockquote" webmail="1" style="border-left: 2px solid blue; margin-left: 8px; padding-left: 8px; font-size:10pt; color:black; font-family:verdana;">
<div id="wmQuoteWrapper">
-------- Original Message --------<br>
Subject: Re: [BUGS] Installing/Upgrading PostgreSQL 9.1.6 to 9.3 known<br>
bugs?<br>
From: Bruce Momjian <<a href="mailto:bruce(at)momjian(dot)us">bruce(at)momjian(dot)us</a>><br>
Date: Wed, October 02, 2013 7:29 am<br>
To: John R Pierce <<a href="mailto:pierce(at)hogranch(dot)com">pierce(at)hogranch(dot)com</a>><br>
Cc: <a href="mailto:pgsql-bugs(at)postgresql(dot)org">pgsql-bugs(at)postgresql(dot)org</a><br>
<br>
On Fri, Sep 20, 2013 at 02:00:05PM -0700, John R Pierce wrote:<br>
> On 9/20/2013 1:51 PM, <a href="mailto:fburgess(at)radiantblue(dot)com">fburgess(at)radiantblue(dot)com</a> wrote:<br>
> <br>
> 1.) During our prior upgrade process we used pg_upgrade to move from pg<br>
> 8.4.3 to 9.1.6 using the hard links install option, we also have our data<br>
> spread across disk storage mediums; fiber, nas. Are there any known issues,<br>
> bugs with using pg_upgrade to move from 9.1.6 to pg 9.3?<br>
> <br>
> <br>
> <br>
> having multiple tablespaces on different mount points complicates things. I'm<br>
> not sure how or if pg_upgrade handles that.<br>
<br>
pg_upgrade is fine with that. The old/new tablespaces stay in the same<br>
mount point as just per-version subdirectories.<br>
<br>
-- <br>
Bruce Momjian <<a href="mailto:bruce(at)momjian(dot)us">bruce(at)momjian(dot)us</a>> <a href="http://momjian.us">http://momjian.us</a><br>
EnterpriseDB <a href="http://enterprisedb.com">http://enterprisedb.com</a><br>
<br>
+ It's impossible for everything to be true. +<br>
<br>
<br>
-- <br>
Sent via pgsql-bugs mailing list (<a href="mailto:pgsql-bugs(at)postgresql(dot)org">pgsql-bugs(at)postgresql(dot)org</a>)<br>
To make changes to your subscription:<br>
<a href="http://www.postgresql.org/mailpref/pgsql-bugs">http://www.postgresql.org/mailpref/pgsql-bugs</a><br>
</div>
</blockquote></span></body></html>