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=jJnEeF7MPvKhnz24A4nvtpyjM9YK7sxs11bSGgQz3PSVqi6ueIeimSK7IUlFSuYk2d
	YY1H2E/9rYLbeXjGc0dNOFkwzmt7eIeH/yr2uIeVXAC8szBJ+tiwrl8Ve81cfQe8BKiU
	EHj4O2y7BdViJFR/catUe5vg1aorouElyCQqE=
Message-ID: <dcc563d10811111112m516209daq48be34c77dce2d07@mail.gmail.com>
Date: Tue, 11 Nov 2008 12:12:55 -0700
From: "Scott Marlowe" <scott.marlowe@gmail.com>
To: "Swathi S" <ss.postgres@gmail.com>
Subject: Re: Ideal way to upgrade to postgres 8.3 with less downtime
Cc: pgsql-admin@postgresql.org
In-Reply-To: <6c1264780811062204t260f7c4eo20675bc8d2b0bb6b@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <6c1264780811062204t260f7c4eo20675bc8d2b0bb6b@mail.gmail.com>

On Thu, Nov 6, 2008 at 11:04 PM, Swathi S <ss.postgres@gmail.com> wrote:
> Hi,
>
> I have a database of size approx 400G. It's a 24/7 database. Only few tables
> have regular reads and writes. The other tables just store information.
>
> I would like to upgrade to 8.3 and would like to know the best way to
> upgrade with less downtime.

Assuming you're running 8.0 or higher now, slony should provide you
with a one stop upgrade path with the minimum amount of downtime.  We
use it for our database which is smaller (~20 Gigs) but quite hard
working, with access around the clock, and we switched out 8.1 to 8.3
with abut 1 minute of downtime.