pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jan Wieck <JanWieck@Yahoo.com>
To: mario.splivalo@mobart.hr
Cc: pgsql-sql@postgresql.org
Subject: Re: why vacuum
Date: Thu, 27 Oct 2005 09:47:17 -0400
Message-ID: <4360DA65.6010601@Yahoo.com> (raw)
In-Reply-To: <1130401371.31435.17.camel@ekim>
References: <200510261015.17623.lawgon@thenilgiris.com>
	<1130339980.2872.12.camel@state.g2switchworks.com>
	<435FAA21.3070400@Yahoo.com>
	<1130401371.31435.17.camel@ekim>

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@Yahoo.com #



view thread (25+ messages)  latest in thread

Message-ID: <4360DA65.6010601@Yahoo.com>
Permalink:  ../4360DA65.6010601@Yahoo.com/
Also on:    postgresql.org/message-id/4360DA65.6010601@Yahoo.com

 · 

reply

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: JanWieck@Yahoo.com, mario.splivalo@mobart.hr
  Subject: Re: why vacuum
  In-Reply-To: <4360DA65.6010601@Yahoo.com>

* 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