Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 717EA1337C29 for ; Wed, 13 Oct 2010 14:47:41 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 37050-01 for ; Wed, 13 Oct 2010 17:46:46 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from asmtpout030.mac.com (asmtpout030.mac.com [17.148.16.105]) by mail.postgresql.org (Postfix) with ESMTP id 8BA871337C2B for ; Wed, 13 Oct 2010 14:07:39 -0300 (ADT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=us-ascii Received: from [10.0.1.13] (173-14-18-13-Colorado.hfc.comcastbusiness.net [173.14.18.13]) by asmtp030.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0LA800K5CNKLIM80@asmtp030.mac.com> for pgsql-general@postgresql.org; Wed, 13 Oct 2010 10:07:35 -0700 (PDT) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=5 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=6.0.2-1004200000 definitions=main-1010130092 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15,1.0.148,0.0.0000 definitions=2010-10-13_08:2010-10-13, 2010-10-13, 1970-01-01 signatures=0 Subject: Re: Copying data files to new hardware? From: Brian Hirt In-reply-to: Date: Wed, 13 Oct 2010 11:07:33 -0600 Cc: Postgresql Mailing List Message-id: References: <7dc101b1-6596-4850-b0ce-cb3f01f51f14@n40g2000vbb.googlegroups.com> To: "Evan D. Hoffman" X-Mailer: Apple Mail (2.1081) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-5 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201010/475 X-Sequence-Number: 168387 Yes, we've used Slony for migrating 8.2 -> 8.3 -> 8.4 and plan an using it to migrate to 9.0 in the near future. You should be able to skip releases as well like you say 8.2 -> 8.4. You'll probably want to test out both slony and 8.4 on your development machines first and make sure everything works okay. It takes a little bit to get familiar with slony, it's not a simple program that you install and click a button to set up replication and have everything happen for you. We spent a fair amount of time writing scripts to work with slony to help support our processes. On Oct 13, 2010, at 10:59 AM, Evan D. Hoffman wrote: > Thanks, Brian & Jaime. Regarding Slony, would that allow for > migration to a new version as well - i.e. moving from 8.2 on the old > machine to 8.4 on the new machine via Slony with minimal downtime? > > The Slony method is one I hadn't considered. Since our database is so > large, even a direct file copy would require some downtime (since we'd > need to stop the DB before beginning the copy). Slony would probably > let us cut the downtime from hours to minutes (dump & restore for us > has historically taken days). > > Thanks again, > Evan