Maybe because when you are "running it without a transaction" you still are.
Say you have this:
Begin
select
update
delete
commit
One transaction. Then you have this:
seelct
update
delete.
You are running three transactions as opposed to one. More overhead I
assume. If you submit a single query to postgres, it is wrapped in a
transaction.
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "Jarmo Paavilainen" <netletter@comder.com>
To: "MYSQL" <mysql@lists.mysql.com>; "PostgreSQL General"
<pgsql-general@postgresql.org>
Sent: Friday, December 29, 2000 1:01 PM
Subject: SV: [GENERAL] MySQL and PostgreSQL speed compare
<snip>
> >>> Sir, thanks for sharing this with us. However, unless you can explain
> >>> why queries inside of transactions run faster than queries outside of
> >>> transactions, I would be inclined to mistrust the test. I haven't
>
> I was suprised too. But the only difference is that I do a "BEGIN" before
I
> start inserting/modifying/deleting and then when Im done I do a "COMMIT".
> Everything between those are exactly the same. Ive been told that MySQL
does
> not support transactions (by default) so there the test is broken. And
with
> PostgreSQL, well something inside PostgreSQL is broken (it cant be right
> that with transaction PostgreSQL is 10 times faster than without).
<snip>
