On Wed, Feb 16, 2005 at 10:12:53AM +0000, ancorgs at banot.net wrote:
> 1) In the master node this query is performed:
>   UPDATE Example_table SET name = 'juan' WHERE key = '4'
> 
>   It's the same query performed in the slave node?
>   (Note that, in fact, it's not necessary)

Yes.  In fact, erserver used to try to avoid propagating such things
to the slave, and the cost wasn't worth the benefit: the overhead was
so great that it killed you.

> 2) Slony-I is stopped in the slave host. Then (without replication) the
>   following query is performed in the slave database:
>   UPDATE Example_table SET name = 'pepe' WHERE key = '4'

This fails on a replicated (subscribed) table.  Slony has a mechanism
to ensure that you don't update a subscribed table, and only update
the origin.

A

-- 
Andrew Sullivan  | ajs at crankycanuck.ca
The fact that technology doesn't work is no bar to success in the marketplace.
		--Philip Greenspun