Re: MySQL / PostgreSQL (was: Postgres object orientation) - Mailing list pgsql-general

From Alain TESIO
Subject Re: MySQL / PostgreSQL (was: Postgres object orientation)
Date
Msg-id 006c01bf58b7$7e57b580$c95f72c3@atesio
Whole thread Raw
In response to RE: [GENERAL] Benchmarks  ("Culberson, Philip" <philip.culberson@dat.com>)
Responses Re: [GENERAL] Re: MySQL / PostgreSQL (was: Postgres object orientation)
List 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





pgsql-general by date:

Previous
From: "Shanthala Rao"
Date:
Subject: please help
Next
From: Gabriel Fernandez
Date:
Subject: Confussion with Table_lock levels and isolation levels.