From: Simon Riggs <simon@2ndquadrant.com>
To: Greg Stark <gsstark@mit.edu>
To: pgsql-hackers@postgresql.org
To: J. Andrew Rogers <jrogers@neopolitan.com>
Subject: Re: PITR for replication?
Date: Fri, 2 Apr 2004 19:57:41 +0100
Message-ID: <KGEFLMPJFBNNLNOOOPLGGEGACHAA.simon@2ndquadrant.com> (raw)
In-Reply-To: <87isgjov70.fsf@stark.xeocode.com>
> Greg Stark
> "J. Andrew Rogers" <jrogers@neopolitan.com> writes:
>
> > I may be completely missing the point here, but it looks to
> me as though
> > the PITR archival mechanism is also most of a native replication
> > facility. Is there anyone reason this couldn't be extended to
> > replication, and if so, is anyone planning on using it as such?
> >
> > My memory is fuzzy on this point, but I seem to recall that this is
> > (was?) how replication is more-or-less done for many of the big
> > commercial RDBMS.
You're right...it is the basis of a log shipping replication facility.
I'm keen no to get too far ahead of ourselves. Let's eat the mammoth one
bite at a time....or one patch at a time.
> Well "replication" is one of those things that means
> different things to
> different people. IMHO, this is one of the simpler, more
> reliable, mechanisms
> and would be nice to have. And you're right that it shouldn't
> require much
> more work, in fact it's probably easier than a lot of other
> cases that PITR
> requires.
I agree. PITR is intended initially as a recovery mechanism. Replication
has other purposes as well, such as locating data close to where it is
required (in master-multi-slave replication scenarios), which is
certainly not an objective or even a likely end point of the PITR work.
The PostgreSQL community is lucky enough to have some very competent
people working on those other approaches and I would recommend everybody
checks out that work.
> For a long time Oracle has supported this mechanism for
> running warm standby
> databases. Basically you maintain a second database and every
> time an archived
> log is finished you ship it over and immediately "restore" it
> on the standby
> machine. Whenever you have a failure you can quickly fail
> over to the standby
> database which is all ready to go and up-to-date within
> minutes of your
> failure.
This facility is one of the intended features, if all goes well. But it
is an advanced feature, not the bread and butter.
> Since 8i Oracle has also supported a more advanced version
> where you can open
> the standby database in read-only mode.
This mode requires more thought, but is certainly possible, in time.
Best Regards
Simon Riggs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-hackers-pitr@postgresql.org
Cc: simon@2ndquadrant.com, gsstark@mit.edu, pgsql-hackers@postgresql.org, jrogers@neopolitan.com
Subject: Re: PITR for replication?
In-Reply-To: <KGEFLMPJFBNNLNOOOPLGGEGACHAA.simon@2ndquadrant.com>
References: <87isgjov70.fsf@stark.xeocode.com> <KGEFLMPJFBNNLNOOOPLGGEGACHAA.simon@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox