DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=lozXneC0vh9Xmzf36OLae3Y0rZvOLIZpbD/2R3ke9Mhz7fru1vdoe6jFxD1RbAgHu90kDxfnIosU8fqZz+K53lZQZMVOxcf53906qG/bvkjs+EcpHmiypzRNQ8Kd2huFPiHnWvch953d6CydprcUd5pUoREkVtytjVGGyfI+mYs=
Message-ID: <432B0627.2030700@gmail.com>
Date: Fri, 16 Sep 2005 10:51:35 -0700
From: Russ Brown <pickscrape@gmail.com>
User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050809)
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: Re: Replication
References: <BF505885.3181F%scott_ribe@killerbytes.com>
In-Reply-To: <BF505885.3181F%scott_ribe@killerbytes.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Scott Ribe wrote:
>>How about a third choice: you can also use a proven, reliable and tested
>>  replication solution that is included in the core system because the
>>core system basiclly provides it anyway.
> 
> 
> Sure, but that one is spelled "Sybase", not "MySQL" ;-)
> 
> 

It's amazing how misunderstood my post was.

My third choice was a hypothetical future version of PostgreSQL, 
modified from its current form very slightly to include a form of 
replication 'out of the box': a couple of scripts to enable WAL log 
transfer and also a solution to the problem of WAL log delay mentioned 
by other posters.

I only mentioned MySQL because their 'out of the box' solution involves 
transferring the binlogs, which is similar to the method of transferring 
the PostgreSQL WAL logs, and it just made me think. That's all. I wasn't 
comparing, I wasn't suggesting MySQL is better than PostgreSQL. I wasn't 
suggesting that they have the 'ultimate' solution. I wasn't even 
suggesting that they have a good solution. It just made me think. That's 
all.

Well, I've learned my lesson. Next time I post I'll be sure not to 
mention MySQL in any way, shape or form.

-- 

Russ