pg.ddx.io pgsql-hackers-pitr@postgresql.org mailing list archive
help / color / mirror / Atom feedPITR for replication?
5+ messages / 5 participants
[nested] [flat]
* PITR for replication?
@ 2004-04-02 00:58 J. Andrew Rogers <jrogers@neopolitan.com>
2004-04-02 01:50 ` Re: PITR for replication? Gavin Sherry <swm@linuxworld.com.au>
2004-04-02 03:04 ` Re: PITR for replication? Christopher Browne <cbbrowne@acm.org>
2004-04-02 04:33 ` Re: PITR for replication? Greg Stark <gsstark@mit.edu>
0 siblings, 3 replies; 5+ messages in thread
From: J. Andrew Rogers @ 2004-04-02 00:58 UTC (permalink / raw)
To: pgsql-hackers@postgresql.org
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.
jrogers@neopolitan.com
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: PITR for replication?
2004-04-02 00:58 PITR for replication? J. Andrew Rogers <jrogers@neopolitan.com>
@ 2004-04-02 01:50 ` Gavin Sherry <swm@linuxworld.com.au>
2 siblings, 0 replies; 5+ messages in thread
From: Gavin Sherry @ 2004-04-02 01:50 UTC (permalink / raw)
To: J. Andrew Rogers <jrogers@neopolitan.com>; +Cc: pgsql-hackers@postgresql.org
On Fri, 1 Apr 2004, J. Andrew Rogers wrote:
>
> 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.
Logfile shipping is one replication option some commercial vendors offer.
It doesn't solve all problems however. It is mostly used for hot backups
in my experience.
Gavin
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: PITR for replication?
2004-04-02 00:58 PITR for replication? J. Andrew Rogers <jrogers@neopolitan.com>
@ 2004-04-02 03:04 ` Christopher Browne <cbbrowne@acm.org>
2 siblings, 0 replies; 5+ messages in thread
From: Christopher Browne @ 2004-04-02 03:04 UTC (permalink / raw)
To: pgsql-hackers@postgresql.org
Oops! jrogers@neopolitan.com ("J. Andrew Rogers") was seen spray-painting on a wall:
> 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.
What isn't clear to me at this point is whether PITR is set up to
allow the database to remain "live and accessible" while updates are
being loaded in.
If that's NOT the case, then it is in no way a meaningful replacement
for replication, vastly useful though it may be.
At those times I have seen Oracle(tm) archive logs being applied to
support PITR-related functionality, the DB hasn't been "up and
running." I suspect that may have changed by now, which would
certainly be handy for replication.
--
(format nil "~S@~S" "cbbrowne" "ntlug.org")
http://cbbrowne.com/info/multiplexor.html
As of next Tuesday, all terminal input will be line-at-a-time.
Please update your programs.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: PITR for replication?
2004-04-02 00:58 PITR for replication? J. Andrew Rogers <jrogers@neopolitan.com>
@ 2004-04-02 04:33 ` Greg Stark <gsstark@mit.edu>
2004-04-02 18:57 ` Re: PITR for replication? Simon Riggs <simon@2ndquadrant.com>
2 siblings, 1 reply; 5+ messages in thread
From: Greg Stark @ 2004-04-02 04:33 UTC (permalink / raw)
To: pgsql-hackers@postgresql.org
"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.
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.
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.
Since 8i Oracle has also supported a more advanced version where you can open
the standby database in read-only mode. This makes it useful for running batch
reports and so on. In postgres this wouldn't work nearly so well since even
read-only queries require write access to the database in postgres. Perhaps
it's not nearly so urgent since running long-running batch queries on a busy
system in postgres doesn't pose all the same dangers it does in Oracle (the
dreaded "snapshot too old" error) -- though there are other analogous dangers
(fsm settings being too small unexpectedly).
--
greg
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: PITR for replication?
2004-04-02 00:58 PITR for replication? J. Andrew Rogers <jrogers@neopolitan.com>
2004-04-02 04:33 ` Re: PITR for replication? Greg Stark <gsstark@mit.edu>
@ 2004-04-02 18:57 ` Simon Riggs <simon@2ndquadrant.com>
0 siblings, 0 replies; 5+ messages in thread
From: Simon Riggs @ 2004-04-02 18:57 UTC (permalink / raw)
To: Greg Stark <gsstark@mit.edu>; pgsql-hackers@postgresql.org; J. Andrew Rogers <jrogers@neopolitan.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
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2004-04-02 18:57 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-04-02 00:58 PITR for replication? J. Andrew Rogers <jrogers@neopolitan.com>
2004-04-02 01:50 ` Gavin Sherry <swm@linuxworld.com.au>
2004-04-02 03:04 ` Christopher Browne <cbbrowne@acm.org>
2004-04-02 04:33 ` Greg Stark <gsstark@mit.edu>
2004-04-02 18:57 ` Simon Riggs <simon@2ndquadrant.com>
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