From: Mario Splivalo <mario.splivalo@mobart.hr>
To: pgsql-sql@postgresql.org
Subject: Re: why vacuum
Date: Thu, 27 Oct 2005 10:22:51 +0200
Message-ID: <1130401371.31435.17.camel@ekim> (raw)
In-Reply-To: <435FAA21.3070400@Yahoo.com>
References: <200510261015.17623.lawgon@thenilgiris.com>
<1130339980.2872.12.camel@state.g2switchworks.com>
<435FAA21.3070400@Yahoo.com>
On Wed, 2005-10-26 at 12:09 -0400, Jan Wieck wrote:
> >
>
> You must have missed the FAQ and other side notes about replication in
> the MySQL manual. Essentially MySQL replication is nothing but a query
> duplicating system, with the added sugar of taking care of now() and
> some other non-deterministic things, but not all of them.
>
> Non-deterministic user defined procedures, functions and triggers will
> simply blow MySQL's sophisticated replication apart.
>
That is just not true. I haven't tried MySQL 4 and above, but in 3.5.x
replication wos working as expected, and the load that replication posed
was insignificant. The only TRUE problem was that replication was
unidirectional. That SAME problem has Slony, and other 'replication
systems' available for postgres.
Mike
--
Mario Splivalo
Mob-Art
mario.splivalo@mobart.hr
"I can do it quick, I can do it cheap, I can do it well. Pick any two."
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: mario.splivalo@mobart.hr
Subject: Re: why vacuum
In-Reply-To: <1130401371.31435.17.camel@ekim>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox