From: | Tino Wildenhain <tino(at)wildenhain(dot)de> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Postgresql-General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL vs. InnoDB performance |
Date: | 2005-06-03 05:44:14 |
Message-ID: | 1117777454.5018.4.camel@Andrea.peacock.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Am Freitag, den 03.06.2005, 00:36 +0200 schrieb Peter Eisentraut:
> On a particular system, loading 1 million rows (100 bytes, nothing
> fancy) into PostgreSQL one transaction at a time takes about 90
> minutes. Doing the same in MySQL/InnoDB takes about 3 minutes. InnoDB
> is supposed to have a similar level of functionality as far as the
> storage manager is concerned, so I'm puzzled about how this can be.
> Does anyone know whether InnoDB is taking some kind of questionable
> shortcuts it doesn't tell me about? The client interface is DBI. This
> particular test is supposed to simulate a lot of transactions happening
> in a short time, so turning off autocommit is not relevant.
Maybe postgres' actually working ref-integrity checks bite here?
That test is a bit vague - maybe we can see more details? :-)
> As you might imagine, it's hard to argue when the customer sees these
> kinds of numbers. So I'd take any FUD I can send back at them. :)
>
From | Date | Subject | |
---|---|---|---|
Next Message | Patrick.FICHE | 2005-06-03 06:50:48 | Re: Using pg_dump in a cron |
Previous Message | David Parker | 2005-06-03 01:43:20 | Re: SQL call to get pid of current connection |