> Yep, WAL collects all database changes into one file.  Easy to see how
> some other host trying to replication a different host would find the
> WAL contents valuable.

Unfortunately, slave database(s) should be on the same platform
(hardware+OS) to be able to use information about *physical*
changes in data files. Also, this would be still *async* replication.
Maybe faster than rserv, maybe with less space requirements (no rserv'
log table), but maybe not.

I believe that making efforts to implement (bi-directional) *sync*
replication would be more valuable.

Vadim

Fri, 27 Apr 2001 17:41:43 -0700
"Mikheev, Vadim" <vmikheev@SECTORBASE.COM>
RE: WAL feature
[ Charset ISO-8859-1 unsupported, converting... ]
> > Yep, WAL collects all database changes into one file.  Easy to see how
> > some other host trying to replication a different host would find the
> > WAL contents valuable.
> 
> Unfortunately, slave database(s) should be on the same platform
> (hardware+OS) to be able to use information about *physical*
> changes in data files. Also, this would be still *async* replication.
> Maybe faster than rserv, maybe with less space requirements (no rserv'
> log table), but maybe not.
> 
> I believe that making efforts to implement (bi-directional) *sync*
> replication would be more valuable.

Or maybe an platform-neutral interface to the WAL file.  Seems this
would fit a need.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Fri, 27 Apr 2001 20:44:39 -0400 (EDT)
Bruce Momjian <pgman@candle.pha.pa.us>
Re: WAL feature