<html><body><span style="font-family:Verdana; color:#000000; font-size:10pt;"><div>We shouldn't have a problem with using pg_upgrade with the hard link option to upgrade from postgreSQL 9.1.6 after I get the spatial component upgraded to postgis 2.1, then straight to postgreSQL 9.3, Right? </div><div><br></div><div>thanks<br></div><div><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: Tue, October 08, 2013 6:17 am<br>
To: <a href="mailto:fburgess(at)radiantblue(dot)com">fburgess(at)radiantblue(dot)com</a><br>
Cc: <a href="mailto:pgsql-bugs(at)postgresql(dot)org">pgsql-bugs(at)postgresql(dot)org</a><br>
<br>
On Mon, Oct 7, 2013 at 08:07:42AM -0700, <a href="mailto:fburgess(at)radiantblue(dot)com">fburgess(at)radiantblue(dot)com</a> wrote:<br>
> Bruce, Proposed Steps. Do they look feasible?<br>
> <br>
> 1.) pg_dump -h localhost -p 5432 -U postgres -Fc -b -v -f "/somepath/<br>
> 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/<br>
> testdb.backup" | psql -h localhost -p 5432 -U postgres newdb 2> errors.txt <-<br>
> this step may run 5-6 days, since our backup runs that long, right?<br>
> 4.) At this point we will have two 6.1TB databases, so it looks like a<br>
> prerequisite is to have available double the db size in disk space, right?<br>
> 5.) then if no critical errors, there will be errors since we have our testdb<br>
> schema in the public folder<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<br>
> 2.1.1, with PostgreSQL 9.1.6<br>
> 7.) then can we just use pg_upgrade with the hard links option, instead of<br>
> copying files to the new cluster option to upgrade to PostgreSQL 9.3?<br>
<br>
Sorry, I have no idea how to upgrade PostGIS.<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>