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

Поиск
Список
Период
Сортировка
От Mikheev, Vadim
Тема Re: [GENERAL] Database replication... - Mission Critica
Дата
Msg-id 3705826352029646A3E91C53F7189E325186B7@sectorbase2.sectorbase.com
обсуждение исходный текст
Ответы Re: [GENERAL] Database replication... - Mission Critica  (Neil Conway <neilc@samurai.com>)
Re: [GENERAL] Database replication... - Mission Critica  ("Shridhar Daithankar" <shridhar_daithankar@persistent.co.in>)
Список 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

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Jason Tishler
Дата:
Сообщение: Re: [CYGWIN] Request for supported platforms
Следующее
От: Florian Litot
Дата:
Сообщение: command