Continuous PITR (was Re: multimaster) - Mailing list pgsql-general

From Ron Johnson
Subject Continuous PITR (was Re: multimaster)
Date
Msg-id 46608859.2060206@cox.net
Whole thread Raw
In response to multimaster (was: Slightly OT.)  (Andrew Sullivan <ajs@crankycanuck.ca>)
Responses Re: Continuous PITR (was Re: multimaster)
Re: Continuous PITR (was Re: multimaster)
List pgsql-general
On 06/01/07 11:16, Andrew Sullivan wrote:
[snip]
>
> My real question in all this is, "What is the problem you are trying
> to solve?"  Hot failover using combinations of hardware and software,
> and a disk array that can be mounted across two machines, is actually
> probably good enough for most cases, assuming it is implemented
> correctly (see recent discussion on this topic).  So the availability
> piece is mostly solved.  What else do you want?

What you need are disk blocks to be mirrored to a machine at the DR
site.  Or "continuous PITR" to the DR machine.

How difficult would it be to modify the process (the postmaster?)
that writes the xlogs(?) to tee them to a listening process across
the cloud on the DR machine, which then applies them to the DR database?

This then begs the question: are CREATE|ALTER TABLESPACE commands
stored in the xlogs?

--
Ron Johnson, Jr.
Jefferson LA  USA

Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!


pgsql-general by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [Fwd: Re: Autovacuum keeps vacuuming a table disabled in pg_autovacuum]
Next
From: Kevin Hunter
Date:
Subject: Re: Seq Scan