X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 4AC9BD1CA65 for ; Sun, 8 Feb 2004 05:01:48 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 41945-10 for ; Sun, 8 Feb 2004 01:01:47 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 6B137D1C517 for ; Sun, 8 Feb 2004 01:01:46 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i1851X4A027998; Sun, 8 Feb 2004 00:01:33 -0500 (EST) To: Palle Girgensohn Cc: pgsql-admin@postgresql.org Subject: Re: reduce downtime when upgrading 7.3 -> 7.4 In-reply-to: <331690000.1076207705@palle.girgensohn.se> References: <331690000.1076207705@palle.girgensohn.se> Comments: In-reply-to Palle Girgensohn message dated "Sun, 08 Feb 2004 03:35:05 +0100" Date: Sun, 08 Feb 2004 00:01:32 -0500 Message-ID: <27997.1076216492@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/115 X-Sequence-Number: 12289 Palle Girgensohn writes: > The most obvious question is, can we use pg_upgrade from contrib? It seems > not to have been updated since 7.3, and is generally documented as > untested. "Guaranteed not to work" is more like it. I have some ambitions of rewriting it for future releases, but don't even think of going there at the moment. regards, tom lane