X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id B058C9FA4DE for ; Fri, 5 May 2006 13:48:56 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 70247-07 for ; Fri, 5 May 2006 13:48:47 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from projects.commandprompt.com (host-130.commandprompt.net [207.173.203.130]) by postgresql.org (Postfix) with ESMTP id ED16F9FA3A3 for ; Fri, 5 May 2006 13:48:46 -0300 (ADT) Received: from [192.168.1.50] (or-67-76-146-141.sta.sprint-hsd.net [67.76.146.141]) (authenticated bits=0) by projects.commandprompt.com (8.13.4/8.13.4) with ESMTP id k45GmaBb028864; Fri, 5 May 2006 09:48:41 -0700 Message-ID: <445B81DD.8070609@commandprompt.com> Date: Fri, 05 May 2006 09:48:29 -0700 From: "Joshua D. Drake" Organization: Command Prompt, Inc. User-Agent: Mail/News 1.5 (X11/20060309) MIME-Version: 1.0 To: arnaulist@andromeiberica.com CC: pgsql-admin@postgresql.org Subject: Re: Best way to upgrade Postgresql 7.4.x to 8.1.x? References: <445B2359.2070004@andromeiberica.com> In-Reply-To: <445B2359.2070004@andromeiberica.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (projects.commandprompt.com [192.168.2.159]); Fri, 05 May 2006 09:48:41 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/57 X-Sequence-Number: 21589 Arnau wrote: > Hi all, > > I have several servers running with Postgresql 7.4.x on Debian, > everybody says that those servers should be migrated to version 8.0 or > 8.1. Finally I'm decided to migrate those servers but I'm worried about > how to do that. Those servers are in production and the downtime should > be the minimum. Any advise about what's the way or the best way to do it? > > Thank you very much I think Slony is going to be the best bet for minimal downtime. -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/