public inbox for [email protected]  

help / color / mirror / Atom feed

From: Thomas O'Connell <[email protected]>
To: [email protected]
To: [email protected]
To: [email protected]
Subject: 7.2.x -> 7.3 upgrade docs?
Date: Wed, 11 Dec 2002 14:43:27 -0600
Message-ID: <[email protected]> (raw)

has anyone put together a Sensible Strategies for Upgrading document 
when moving from 7.2.x to 7.3?

for instance, i've read in a few different places that not all 
dependencies will be appropriately created.

as an admin, my biggest questions are:

1. is it necessary, strongly recommended, recommended, or irrelevant to 
run contrib/adddepend?

2. is it necessary, strongly recommended, recommended, or irrelevant to 
upgrade DBD::Pg for people accessing postgres via the Perl DBI? speaking 
of which, are there docs about what changed in the latest DBD::Pg?

3. what is the default environment as far as schemas are concerned for 
databases that have been migrated? is there just a public schema created 
for all objects? is it possible to move existing tables into 
user-created schemas? i didn't see an ALTER TABLE SET SCHEMA...

4. are there other important considerations i might be overlooking?

i've read the new docs, but the upgrade section remains much the same as 
previous versions, despite the fact that there seem to be enough catalog 
changes between 7.2 and 7.3 that admins ought to be paying attention to 
more details than are presented there. so far, the reading i've done has 
provided a varying amount of detail in a variety of places: the new 
version of the docs, the HISTORY file, the mailing lists; but nothing 
i've yet seen gives a complete picture of the important details to be 
considered when upgrading. maybe the details aren't as important as i'm 
guessing? i kind of feel otherwise, though.

thanks!

-tfo

Thomas F. O'Connell
DBA | Systems Programmer
Monster Labs, Inc.
http://www.monsterlabs.com/
110 30th Avenue North, Suite 1
Nashville, TN 37203
phone: 615-301-2600 x132
fax: 615-301-2602

view thread (4+ messages)  latest in thread

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 using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: 7.2.x -> 7.3 upgrade docs?
  In-Reply-To: <[email protected]>

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

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