RE: AW: Postgres Replication - Mailing list pgsql-hackers

From Mikheev, Vadim
Subject RE: AW: Postgres Replication
Date
Msg-id 3705826352029646A3E91C53F7189E32016670@sectorbase2.sectorbase.com
Whole thread Raw
In response to AW: Postgres Replication  (Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at>)
List pgsql-hackers
> Here are some disadvantages to using a "trigger based" approach:
> 
> 1) Triggers simply transfer individual data items when they 
> are modified, they do not keep track of transactions.

I don't know about other *async* replication engines but Rserv
keeps track of transactions (if I understood you corectly).
Rserv transfers not individual modified data items but
*consistent* snapshot of changes to move slave database from
one *consistent* state (when all RI constraints satisfied)
to another *consistent* state.

> 4) The activation of triggers in a database cannot be easily
> rolled back or undone.

What do you mean?

Vadim


pgsql-hackers by date:

Previous
From: Philip Crotwell
Date:
Subject: Re: Re: [JDBC] unlink large objects
Next
From: Hannu Krosing
Date:
Subject: Re: Implicit order-by in Postgresql?