Re: [HACKERS] Database replication... - Mission Critica

From: "Mikheev, Vadim" <VMIKHEEV(at)sectordata(dot)com>
To: "'Bill Gribble'" <grib(at)linuxdevel(dot)com>, Greg Patnude <GPatnude(at)adelphia(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org
Subject: Re: [HACKERS] Database replication... - Mission Critica
Date: 2002-11-04 20:23:23
Message-ID: 3705826352029646A3E91C53F7189E325186B7@sectorbase2.sectorbase.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

> My presumption would be that if you initialize 2 databases to
> a known identical start, have all the same triggers and rules
> on both, then send all queries to both databases, you will
> have 2 identical databases at the end.

This is wrong assumption. If

1st client executes UPDATE t SET a = 1 WHERE b = 2;
2nd client executes UPDATE t SET a = 2 WHERE b = 2;

at "the same time" you don't know in what order these
queries will be executed on two different servers (because
you can't control what transaction will lock record(s)
for update first).

Vadim

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Antonio G. - Geotronix 2002-11-04 20:32:28 Re: Can't import databases with pg_dump. Why?
Previous Message Tom Lane 2002-11-04 20:16:56 Re: TIMESTAMP and PgPL/SQL

Browse pgsql-hackers by date

  From Date Subject
Next Message Marc G. Fournier 2002-11-04 20:23:55 Re: v7.3Beta4 Tag'd and Packaged ...
Previous Message Jason Tishler 2002-11-04 20:05:25 Re: [HACKERS] ipc-daemon