From: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
---|---|
To: | mario(dot)splivalo(at)mobart(dot)hr |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: why vacuum |
Date: | 2005-10-27 13:47:17 |
Message-ID: | 4360DA65.6010601@Yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On 10/27/2005 4:22 AM, Mario Splivalo wrote:
> 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.
Read again. "Non-deterministic user defined procedures ...". Please give
me *ONE* example of a user defined procedure in 3.5.x at all. You must
have missed the point that stored procedures are a new feature in 5.0.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2005-10-27 14:12:41 | Re: why vacuum |
Previous Message | Richard Huxton | 2005-10-27 13:21:15 | Re: why vacuum |