Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 419D4476213; Wed, 11 Dec 2002 19:24:12 -0500 (EST) Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by postgresql.org (Postfix) with ESMTP id E9BCE476281; Wed, 11 Dec 2002 19:22:49 -0500 (EST) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id gBC0MhO11893; Wed, 11 Dec 2002 19:22:43 -0500 (EST) From: Bruce Momjian Message-Id: <200212120022.gBC0MhO11893@candle.pha.pa.us> Subject: Re: 7.2.x -> 7.3 upgrade docs? In-Reply-To: To: "Thomas O'Connell" Date: Wed, 11 Dec 2002 19:22:43 -0500 (EST) Cc: pgsql-admin@postgresql.org, pgsql-docs@postgresql.org, pgsql-general@postgresql.org X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200212/161 X-Sequence-Number: 6656 Thomas O'Connell wrote: > 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? Depends if you want that dependency --- I certainly would. > 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? I would. The new version has changes from the past 18 months. > 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. Yes, we aren't great about presenting release information in a 100% complete way. FYI, the system catalog changes relate mostly to interface/tool authors, so it doesn't appear prominently. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073