Re: Notes on converting from MySQL 5.0.x to PostgreSQL - Mailing list pgsql-general

From Jim C. Nasby
Subject Re: Notes on converting from MySQL 5.0.x to PostgreSQL
Date
Msg-id 20060701001331.GR17241@pervasive.com
Whole thread Raw
In response to Re: Notes on converting from MySQL 5.0.x to PostgreSQL  (David Fetter <david@fetter.org>)
Responses Re: Notes on converting from MySQL 5.0.x to PostgreSQL  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Fri, Jun 30, 2006 at 11:01:19AM -0700, David Fetter wrote:
> On Fri, Jun 30, 2006 at 01:41:53PM -0400, Tom Lane wrote:
> > David Fetter <david@fetter.org> writes:
> > > On Fri, Jun 30, 2006 at 11:39:04AM -0400, Tom Lane wrote:
> > >> It might be worth pointing out that mysql's replication falls
> > >> over if you so much as look at it crosseyed.  I have not had to
> > >> use it for production purposes, but I can tell you that the mysql
> > >> replication regression tests fail ... irreproducibly of course
> > >> ...  almost one time in two in Red Hat's build environment.
> >
> > > Are those tests, or at least descriptions of them, available?
> >
> > Sure, it's just the standard "make test" sequence in mysql's source.
>
> Uh oh.  I'm a little worried about writing tests based on GPLed code
> for Slony-I or other replication systems.  Might these need to be
> clean-roomed?

Is there actually a lack of ideas for our regression tests, or a lack of
people/motivation to work on them?
--
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

pgsql-general by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Is it possible to disable insert/update/delete triggers for one transaction and not another?
Next
From: "Jim C. Nasby"
Date:
Subject: Re: Notes on converting from MySQL 5.0.x to PostgreSQL