Installing/Upgrading PostgreSQL 9.1.6 to 9.3 known bugs?
<html><body><span style="font-family:Verdana; color:#000000; font-size:10pt;"><div>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?<br><br>2.) We also have to stand up a fresh install of pg 9.3 with postgis 2.1 and restore the data from a 9.1.6 dump. Are there any known issues, bugs with using pg_dump or pg_dumpall and then pg_restore to get this done?<br><br><br>thanks<br mce_bogus="1"></div></span></body></html>
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.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
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
<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@momjian.us">bruce@momjian.us</a>><br>
Date: Wed, October 02, 2013 7:29 am<br>
To: John R Pierce <<a href="mailto:pierce@hogranch.com">pierce@hogranch.com</a>><br>
Cc: <a href="mailto:pgsql-bugs@postgresql.org">pgsql-bugs@postgresql.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@radiantblue.com">fburgess@radiantblue.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@momjian.us">bruce@momjian.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@postgresql.org">pgsql-bugs@postgresql.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>
Import Notes
Resolved by subject fallback
On Mon, Oct 7, 2013 at 08:07:42AM -0700, fburgess@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-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?
Sorry, I have no idea how to upgrade PostGIS.
--
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
<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@momjian.us">bruce@momjian.us</a>><br>
Date: Tue, October 08, 2013 6:17 am<br>
To: <a href="mailto:fburgess@radiantblue.com">fburgess@radiantblue.com</a><br>
Cc: <a href="mailto:pgsql-bugs@postgresql.org">pgsql-bugs@postgresql.org</a><br>
<br>
On Mon, Oct 7, 2013 at 08:07:42AM -0700, <a href="mailto:fburgess@radiantblue.com">fburgess@radiantblue.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@momjian.us">bruce@momjian.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@postgresql.org">pgsql-bugs@postgresql.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>
Import Notes
Resolved by subject fallback