Re: Moving Tablespaces

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: Doug McNaught <doug(at)mcnaught(dot)org>
Cc: Allen Fair <dba(at)girders(dot)org>, pgsql-general(at)postgresql(dot)org
Subject: Re: Moving Tablespaces
Date: 2006-01-06 00:23:05
Message-ID: 20060106002305.GG43311@pervasive.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

You can also use WAL log shipping; there's been recent discussion about
that on -admin.

BTW, I'm seeing duplicated emails from you...

On Tue, Jan 03, 2006 at 08:31:09PM -0500, Doug McNaught wrote:
> Allen Fair <dba(at)girders(dot)org> writes:
>
> > Our databases can get large and we want to find the best way to plan for
> > when a database outgrows its current server.
> >
> > How about a replication scheme and cutover? If so, is there a preferred
> > replication package to support this?
>
> Slony-I was designed for this scenario (among others) and is actively
> developed. There are also other replication solutions, some of them
> proprietary.
>
> -Doug
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>

--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jim C. Nasby 2006-01-06 00:29:04 Re: create summaries and update a second table?
Previous Message Qingqing Zhou 2006-01-05 23:49:35 Re: Hardware recommendation for PostgreSQL on Windows?