Re: MySQL / PostgreSQL (was: Postgres object orientation)

From: "Alain TESIO" <tesio(at)easynet(dot)fr>
To: <pgsql-general(at)hub(dot)org>
Cc: <Guillaume(dot)Rousse(at)univ-reunion(dot)fr>
Subject: Re: MySQL / PostgreSQL (was: Postgres object orientation)
Date: 2000-01-07 02:32:42
Message-ID: 006c01bf58b7$7e57b580$c95f72c3@atesio
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-general

> Subsidiary question : why is mySQL excluded from RDBMS
> comparison on postgress www site ?

Maybe because it's much faster ;)
Sure, MySQL doesn't support transactions, rollbacks, ...
Maybe this question will sound a bit naive, but why doesn't
we have the choice to send queries to PostgreSQL as
transactional or not ? It's probably not meaningful to
say that a single query is transactional or not, but what
about a global parameter at the server level ? Forgive me
again for the naivety of this question, this may mean to
have two completely different engines. And it would have
been already done if possible ...

I've compared both engines and MySQL is much faster.
However I'll need transaction to ensure reliability
for the database updates. I've thought at using PostgreSQL
for updates, and MySQL for select, the database being
dumped from PostgreSQL and reloaded into MySQL every
night. Probably with specific queries and scripts rather
than a dump to get a MySQL-compliant dump file.
Has anyone an experience about a similar solution ?

Alain

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Dustin Sallings 2000-01-07 02:42:12 RE: [GENERAL] Benchmarks
Previous Message Culberson, Philip 2000-01-06 20:58:21 RE: [GENERAL] Benchmarks

Browse pgsql-general by date

  From Date Subject
Next Message Dustin Sallings 2000-01-07 02:42:12 RE: [GENERAL] Benchmarks
Previous Message Rudy Gireyev 2000-01-07 01:59:55 Re: [GENERAL] Benchmarks (Vacuum)