[ale] database conversion

[Christopher Fowler]

One method I thought of was to create a system in which there is
wrappers my code uses that will send inserts to multiple servers. 
Problem is that this system is not very robust.

On Thu, 2005-02-10 at 09:51, James P. Kinney III wrote:
> More brainstorming (after a mail crash yesterday!)
> 
> Postgresql 8 has a pretty good Write Ahead Logging. A seperate project I
> am looking at is to use the WAL as a way to syncronize two databases
> that are not in a mirror mode of any type.
> 
> The scenario: Main DB has the _real_ web transactions, user list,
> products, etc.  Second machine gats a clone of the main machine at a
> point in time. Second machine is hauled to a trade show where the net
> access is (or lack) prevents a direct line to the main db.
> 
> Second machine runs the transaction locally after a checkpoint in the
> WAL is set. After the show, the WAL is replayed back into the main
> machine to merge in the transactions from the satellite unit.
> 
> Other than the obvious issues of duplicated transactions (not likely
> except for possibly adding a new user) and the sequence id's for the
> transactions (I will have to double check that the sequencing id's are
> only used as record counters), are there any "gotcha's" that others have
> run across in anything similar?