pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christopher Browne <cbbrowne@acm.org>
To: pgsql-admin@postgresql.org
Subject: Re: replication between mysql 3.23 and postgresql 7.2.4?
Date: Wed, 08 Sep 2004 10:56:41 -0400
Message-ID: <m34qm8stau.fsf@wolfe.cbbrowne.com> (raw)
References: <20040908122513.80296.qmail@web51905.mail.yahoo.com>

A long time ago, in a galaxy far, far away, k_b0000@yahoo.se (k b) wrote:
> Hello.
>
> I have a slightly off topic question.
> Is it possible to set up replication between a mysql
> 3.23.56 server and a postgresql 7.2.4 server without
> any extra software in between?
>
> i am primarily interested in replication from the
> mysql server to the postgresql server, but two way
> replication might be needed later on.
>
> is it possible?
> where can i find more information?

You might look at how MySQL's "native" replication schemes are
implemented, and see if there is some way to adapt them to generate
SQL statements that could be injected into a PostgreSQL instance.

But what this amounts to is "rolling your own solution."

It also strikes me as a good instance of a "fool's errand," as the
semantics of the systems are so strikingly different that you'll find
that if you _do_ implement some form of replication, it won't work
nearly as well as you would hope or need.  

The comments comparing MySQL with Oracle seem pretty appropriate
<http://sql-info.de/mysql/vs/mysql-oracle.html;

Notably:

  "If you find your application works as equally well on Oracle as it
  does on MySQL, then you are vastly underutilising Oracle and
  probably paying for it as well."

In the case of PostgreSQL, you may not be paying anything for it, but
you certainly won't be getting any benefit out of it if you use it
exactly the same as you use MySQL.

And why PostgreSQL 7.2.4?  That's a fairly ancient version, now.  If
you're prepared to do something as experimental as building a two-way
replication system between MySQL and PostgreSQL, jumping straight to
8.0 won't introduce any risks that would be noticeable in comparison
to the ones you already face.  The 'conservative' approach would be to
use 7.4.3, anyways.

You might as well not bother; that will involve a whole lot less
effort, and leave you less disgruntled at the end of the process.
-- 
"cbbrowne","@","cbbrowne.com"
http://cbbrowne.com/info/sgml.html
I just got skylights put in my place. The people who live above me are
furious.



view thread (3+ messages)

Message-ID: <m34qm8stau.fsf@wolfe.cbbrowne.com>
Permalink:  ../m34qm8stau.fsf@wolfe.cbbrowne.com/
Also on:    postgresql.org/message-id/m34qm8stau.fsf@wolfe.cbbrowne.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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: cbbrowne@acm.org
  Subject: Re: replication between mysql 3.23 and postgresql 7.2.4?
  In-Reply-To: <m34qm8stau.fsf@wolfe.cbbrowne.com>
  References: <20040908122513.80296.qmail@web51905.mail.yahoo.com> <m34qm8stau.fsf@wolfe.cbbrowne.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