X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id F08E211F664D for ; Wed, 29 Mar 2006 08:38:37 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 17624-08 for ; Wed, 29 Mar 2006 08:38:37 -0400 (AST) Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id B65E811F6647 for ; Wed, 29 Mar 2006 08:38:35 -0400 (AST) Received: from pat.uio.no (pat.uio.no [129.240.10.6]) by svr4.postgresql.org (Postfix) with ESMTP id 981A95AF06F for ; Wed, 29 Mar 2006 12:38:36 +0000 (GMT) Received: from mail-mx4.uio.no ([129.240.10.45]) by pat.uio.no with esmtp (Exim 4.43) id 1FOZwV-0004oe-Vb for pgsql-admin@postgresql.org; Wed, 29 Mar 2006 14:38:32 +0200 Received: from linus.uio.no ([129.240.201.19]) by mail-mx4.uio.no with esmtps (TLSv1:AES256-SHA:256) (Exim 4.43) id 1FOZwR-0003nm-NG; Wed, 29 Mar 2006 14:38:27 +0200 Message-ID: <442A7FC3.4060600@usit.uio.no> Date: Wed, 29 Mar 2006 14:38:27 +0200 From: Ola Sandbu Organization: USIT/SAPP-DBA User-Agent: Thunderbird 1.5 (X11/20051201) MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: Bloated pg_shdepend_depender_index References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-UiO-Spam-info: not spam, SpamAssassin (score=-5.052, required 12, autolearn=disabled, AWL -0.05, UIO_MAIL_IS_INTERNAL -5.00) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.04 required=5 tests=[AWL=0.040] X-Spam-Score: 0.04 X-Spam-Level: X-Archive-Number: 200603/337 X-Sequence-Number: 21094 Andy Shellam wrote: > This is true, but you could run the new version on the same server/different > port to the current version, and do a simultaneous dump/restore without > having to use extra disk space, or taking your production database offline - > then you can schedule a time to kill the old one, re-assign the port on the > new one and bring it up - would take about 30 seconds, and this could be > done at a time when traffic was at its lowest. > Hmmm - Interesting solution! Does you know of anybody that have tried an upgrade migration like this, and experience with very large databases? -- ------------------------------------- Ola Sandbu tel: (+47)22840197 USIT/SAPP-DBA mob: (+47)91594704 mailto:Ola.Sandbu@usit.uio.no -------------------------------------