Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id BB92A2E0113 for ; Tue, 13 May 2008 11:50:03 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 28177-05-5 for ; Tue, 13 May 2008 11:49:43 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.180]) by developer.postgresql.org (Postfix) with ESMTP id 389302E0120 for ; Tue, 13 May 2008 11:38:01 -0300 (ADT) Received: by py-out-1112.google.com with SMTP id d37so3296618pye.29 for ; Tue, 13 May 2008 07:37:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=qgUSCdH9fnDoG3t/6QoXy8NWHL6DR7r1zYm8B1KsYMs=; b=Q2kCvEIKR/NwNaPPTUcFIEg4axA1yB9e7TWlAL0Z6WSp0qB/kvMUNuotJBRyPEaHg+LVMNOAZtpIoFQ4JSUw+M8ADAB1o5kRe7fKKgv/crM/Cs2uyopcoNTjihGHXWUXIQ7jX8xxGgqe7e2Vufm97ZVZyhLKIv0+Kezj6XSqaCg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=MQmoLta9rdvruAWQCl9yZ4eqzfJn58vJ+bF46YKB65PKPH6vqe1mH6YX02Jti8vtiSEpREzPHF5XwalKTxShYFgeHH4jzSz6/ht3H1W7PCLVnixBZBZhQHRWWJcGs/XzCfpv17VVg7k5U1UBe42pCaNlvg+pEHvh4v8VRcS/NKA= Received: by 10.114.175.16 with SMTP id x16mr9265398wae.12.1210689479163; Tue, 13 May 2008 07:37:59 -0700 (PDT) Received: by 10.114.137.7 with HTTP; Tue, 13 May 2008 07:37:59 -0700 (PDT) Message-ID: Date: Tue, 13 May 2008 08:37:59 -0600 From: "Scott Marlowe" To: "Knight, Doug" Subject: Re: Installation Steps to migrate to Postgres 8.3.1 Cc: "Gauri Kanekar" , pgsql-performance@postgresql.org In-Reply-To: <8536F69C1FCC294B859D07B179F069440DC1B69F@EXCHANGE.ad.wsicorp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <7e4ba9550805122240j7ed6a494hfc10a8b08dad073e@mail.gmail.com> <8536F69C1FCC294B859D07B179F069440DC1B69F@EXCHANGE.ad.wsicorp.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200805/164 X-Sequence-Number: 30132 On Tue, May 13, 2008 at 6:00 AM, Knight, Doug wrote: > Hi, > Along these lines, the usual upgrade path is a pg_dump/pg_restore set. > However, what if your database is large (> 50GB), and you have to > minimize your downtime (say less than an hour or two). Any suggestions > on how to handle that kind of situation? It sure would be nice to have > some kind of tool to update in-place a database, though I know that's > not a likely path. look up Slony