Re: Streaming replication, loose ends

On Fri, 2010-01-15 at 05:36 -0500, Bruce Momjian wrote:
> Heikki Linnakangas wrote:
> > I've now committed streaming replication. I moved the files around a
> > bit, and put the walreceiver/walsender stuff in a new
> > src/backend/replication subdirectory. There's enough stuff there already
> > to deserve a new subdirectory, and if we add the capability for
> > streaming base backups etc. that has been discussed, we will have more
> > code in there.
> > 
> > But it's not time to party yet. There's still a few loose ends we need
> > to address:
> > 
> > Documentation. The patch originally moved around some sections, but I
> > didn't include that in the committed version, to make it clear in the
> > diff what exactly was added/changed. But I do agree with the original
> > thought of adding a new "Replication" chapter, and moving all the
> > replication and standby related stuff there from the "Backup and
> > Restore" chapter, so let's start working on that.
> 
> Uh, do we really want to call this "replication" rather than archive log
> streaming or something.  It seems "replication" is a generic term and
> will confuse people who are using other replication solutions like
> Slony.

+1, it is not replication. I would call it something like continuous
archiving or streaming pitr

Joshua D. Drake


> 
> -- 
>   Bruce Momjian  <bruce@momjian.us>        http://momjian.us
>   EnterpriseDB                             http://enterprisedb.com
> 
>   + If your life is a hard drive, Christ can be your backup. +
> 


-- 
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 503.667.4564
Consulting, Training, Support, Custom Development, Engineering
Respect is earned, not gained through arbitrary and repetitive use or Mr. or Sir.