From: | Grega Bremec <gregab(at)p0f(dot)net> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: sql-bench |
Date: | 2006-09-15 00:11:23 |
Message-ID: | 1158279083.6369.15.camel@aspirinix.p0f.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Tom Lane wrote:
> >> It'd be interesting to see what mysql's performance looks like on this
> >> test using innodb tables, which should be compared against fsync = true
> >> ... but I don't know how to change it to get all the tables to be
> >> innodb.)
Just a point (I've taught some MySQL courses before, sorry 'bout that;
if you're not, I am, sort of :)) - the crash-proof version of
transactional tables in MySQL was supposed to be the Berkeley ones, but
(oh, the irony) they're still beta. InnoDB were just supposed to be
optimized to perform well with loads of data and a mediocre amount of
clients, and *finally* support referential integrity and the rest of the
lot.
Anyways... with Oracle buying off all that stuff, don't even know if it
still matters: the incantation is to either add the ENGINE= or TYPE=
clause after each CREATE TABLE statement, which would look like
CREATE TABLE foo (
...
) ENGINE=InnoDB;
or specify the --default-storage-engine or --default-table-type server
startup option (or, alternatively, set the default-storage-engine or
default-table-type option in my.cnf).
The trick being, mysqldump will be quite explicit in CREATE TABLE
statements, so a vi(1) and a regular expression will probably be needed.
Kind regards,
--
Grega Bremec
gregab at p0f dot net
From | Date | Subject | |
---|---|---|---|
Next Message | Steinar H. Gunderson | 2006-09-15 00:32:39 | Re: sql-bench |
Previous Message | Michael Stone | 2006-09-15 00:08:21 | Re: Vacuums on large busy databases |