[ale] database conversion

[Christopher Fowler]

Stored Procedures is also another nice feature of Postgress.  One thing
I want to do is have backup databases.

In the MySQL realm all that was done with a Master -> Slave and done
with binary data.  I'm not looking for Master->Slave.  I've have had so
many problems getting the Master->Slave working and continue to work
under MySQL.  I want backup databases and possible even load balancing. 
Where I can have 2 database servers and then my application can contact
the first one available.

Maybe Oracle has this and not Postgress or MySQL?


On Wed, 2005-02-09 at 06:25, David Corbin wrote:
> Not that I have anything against PostgreSql, but when the database is built 
> 'properly'  MySql does have transactional support.  Have you considered 
> sticking with MySql and using the InnoDB engine?  It would probably mean much 
> less concern about 'switching'.
> 
> David
> 
> On Tuesday 08 February 2005 09:35 pm, James P. Kinney III wrote:
> > I am looking at a project that will involve migration of a MySql
> > database to PostgreSQL. The original db has numerous design errors that
> > are beginning to cause problems. The move to PostgreSQL will add the
> > transaction capabilities that would have prevented the current problem
> > causing the project (seqential transaction ID's would have been a great
> > start!)
> >
> > As this will need to be a parallel pair of db's for a while to run final
> > tests, I'm looking at pitfalls and processes others have used to migrate
> > from one 24x7 db to another seamlessly. I'm also looking for pointers on
> > getting identical data simultaneously into two seperate db's without
> > having to rewrite the entire app first.
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale