pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Burgholzer, Robert (DEQ) <Robert.Burgholzer@deq.virginia.gov>
To: Marcos Cano <mcano@stsa.info>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: PG_UPGRADE major issue
Date: Thu, 20 Jun 2013 17:01:32 +0000
Message-ID: <77F5F8FA4B407F43BFCFD3FC3478969147C803@COVMSGCES-MBX01> (raw)
In-Reply-To: <1371746106173-5760168.post@n5.nabble.com>
References: <1371661777006-5759906.post@n5.nabble.com>
	<77F5F8FA4B407F43BFCFD3FC3478969147BE32@COVMSGCES-MBX01>
	<1371746106173-5760168.post@n5.nabble.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

Marcos,
This answer might be best put over on the postGIS listserv, but I will suggest a couple of strategies based on some differing assumptions and certainties.

One certainty - it seems that you absolutely have to have some form of PostGIS installed in order to perform the postgreSQL upgrade using pg_upgrade.
One variable - whether or not you will have to do the "hard upgrade" required by the postGIS version when doing the standard PostgreSQL upgrade.  In other 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, then 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 assist in whatever way I might.

Regards,
r.b.




-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



view thread (5+ messages)  latest in thread

Message-ID: <77F5F8FA4B407F43BFCFD3FC3478969147C803@COVMSGCES-MBX01>
Permalink:  ../77F5F8FA4B407F43BFCFD3FC3478969147C803@COVMSGCES-MBX01/
Also on:    postgresql.org/message-id/77F5F8FA4B407F43BFCFD3FC3478969147C803@COVMSGCES-MBX01

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: Robert.Burgholzer@deq.virginia.gov, mcano@stsa.info
  Subject: Re: PG_UPGRADE major issue
  In-Reply-To: <77F5F8FA4B407F43BFCFD3FC3478969147C803@COVMSGCES-MBX01>
  References: <1371661777006-5759906.post@n5.nabble.com> <77F5F8FA4B407F43BFCFD3FC3478969147BE32@COVMSGCES-MBX01> <1371746106173-5760168.post@n5.nabble.com> <77F5F8FA4B407F43BFCFD3FC3478969147C803@COVMSGCES-MBX01>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox