From: | "Willis, Ian (Ento, Canberra)" <Ian(dot)Willis(at)ento(dot)csiro(dot)au> |
---|---|
To: | "'David Wall'" <d(dot)wall(at)computer(dot)org>, pgsql-general(at)postgresql(dot)org |
Subject: | RE: MySQL has transactions |
Date: | 2001-01-24 05:45:44 |
Message-ID: | D21A20CD84607E409F314E31F0F68D8A02BF10@cricket-be.ento.csiro.au. |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
speed with tranactions on
row level locking
I though that postgresql had more data type
extensable interface
choice of index types
better performance under load
triggers
to name a few. Has anyone actually benchmarked mySQL with transations
enabled?
-----Original Message-----
From: David Wall [mailto:d(dot)wall(at)computer(dot)org]
Sent: Wednesday, 24 January 2001 3:30 PM
To: pgsql-general(at)postgresql(dot)org
Subject: [GENERAL] MySQL has transactions
Now that MySQL has transaction support through Berkeley DB lib, and it's
always had way more data types, what are the main advantages postgresql has
over it? I don't think mysql has subselects and such, but they did add a
master-slave replication feature as well as online reorganization (perhaps
locks tables like vacuum?).
Anybody used both of the current releases who can comment?
Thanks,
David
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Leibel | 2001-01-24 06:09:06 | Re: MySQL has transactions |
Previous Message | John Frank | 2001-01-24 05:27:54 | Out of overflow pages. Out of luck. |