From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | Richard Huxton <dev(at)archonet(dot)com> |
Cc: | mario(dot)splivalo(at)mobart(dot)hr, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: why vacuum |
Date: | 2005-10-27 17:52:15 |
Message-ID: | 20051027175215.GJ63747@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Thu, Oct 27, 2005 at 02:21:15PM +0100, Richard Huxton wrote:
> So - if your statement contains something non-deterministic that isn't
> catered for in Mysql's code then it will break.
>
> At it's simplest - if I write a function my_random() and then do:
> UPDATE foo SET a=1 WHERE b < my_random();
> IF my_random() returns different results on different machines, then the
> replication will be broken. See the manual entry below:
> http://dev.mysql.com/doc/refman/5.0/en/replication-features.html
>
> That's not to say the system is worthless - it works fine for many
> people. But it does have limitations.
And you can easily have multi-master syncronous replication in
PostgreSQL using the same idea; just see pgCluster.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Abhishek | 2005-10-27 18:00:41 | combining records from a single table and presenting them as one record |
Previous Message | Jim C. Nasby | 2005-10-27 17:46:01 | Re: How to speed up the database query? |