Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UpiF4-0004i4-AM for pgsql-admin@arkaria.postgresql.org; Thu, 20 Jun 2013 17:01:50 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1UpiF3-0003Wu-Qq for pgsql-admin@arkaria.postgresql.org; Thu, 20 Jun 2013 17:01:49 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UpiF3-0003Wo-4c for pgsql-admin@postgresql.org; Thu, 20 Jun 2013 17:01:49 +0000 Received: from cmailc.vita.virginia.gov ([166.67.65.183]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UpiEw-00023o-B3 for pgsql-admin@postgresql.org; Thu, 20 Jun 2013 17:01:48 +0000 X-SBRS: None X-HAT: Group: RELAYLIST_WHITELIST, Policy: $RELAYED_WHITELIST X-IronPort-AV: E=Sophos;i="4.87,906,1363147200"; d="scan'208";a="6100176" Received: from unknown (HELO COVMSGCES-HUB03.cov.virginia.gov) ([10.192.2.219]) by CRelayC.vita.virginia.gov with ESMTP/TLS/AES128-SHA; 20 Jun 2013 13:01:36 -0400 Received: from COVMSGCES-MBX01.cov.virginia.gov ([10.192.2.206]) by COVMSGCES-HUB03.cov.virginia.gov ([10.192.2.219]) with mapi id 14.02.0318.004; Thu, 20 Jun 2013 13:01:34 -0400 From: "Burgholzer, Robert (DEQ)" To: Marcos Cano , "pgsql-admin@postgresql.org" Subject: Re: PG_UPGRADE major issue Thread-Topic: [ADMIN] PG_UPGRADE major issue Thread-Index: AQHObSHQSXMXAJgFd0KoULUbYQMop5k9b1ZIgAGhsgD//8J/MA== Date: Thu, 20 Jun 2013 17:01:32 +0000 Message-ID: <77F5F8FA4B407F43BFCFD3FC3478969147C803@COVMSGCES-MBX01> References: <1371661777006-5759906.post@n5.nabble.com> <77F5F8FA4B407F43BFCFD3FC3478969147BE32@COVMSGCES-MBX01> <1371746106173-5760168.post@n5.nabble.com> In-Reply-To: <1371746106173-5760168.post@n5.nabble.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.173.211.82] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Pg-Spam-Score: -5.5 (-----) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Marcos, This answer might be best put over on the postGIS listserv, but I will sugg= est a couple of strategies based on some differing assumptions and certaint= ies. One certainty - it seems that you absolutely have to have some form of Post= GIS installed in order to perform the postgreSQL upgrade using pg_upgrade. One variable - whether or not you will have to do the "hard upgrade" requir= ed by the postGIS version when doing the standard PostgreSQL upgrade. In o= ther words -- is the postgreSQL upgrade essentially doing the same as the "= hard upgrade"? If YES - then install postgis 1.3.x on your 9.2.4 then use pg_upgrade, t= hen do the pgis hard upgrade If NO - install postgis 2.x on your 9.2.4 then use pg_upgrade This is a very relevant case study, one that I myself will be going through= very very shortly here so I am interested to follow your progress and assi= st in whatever way I might. Regards, r.b. --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin