| From: | David Fetter <david(at)fetter(dot)org> |
|---|---|
| To: | Decibel! <decibel(at)decibel(dot)org> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-advocacy(at)postgresql(dot)org, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Lukas Kahwe Smith <smith(at)pooteeweet(dot)org>, Jeff Davis <pgsql(at)j-davis(dot)com>, Greg Smith <gsmith(at)gregsmith(dot)com> |
| Subject: | Re: PostgreSQL vs. MySQL: fight |
| Date: | 2007-08-15 02:00:05 |
| Message-ID: | 20070815020005.GA12471@fetter.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
On Tue, Aug 14, 2007 at 05:34:14PM -0500, Decibel! wrote:
> On Mon, Aug 13, 2007 at 10:16:15PM -0700, Josh Berkus wrote:
> > Pavel,
> >
> > > I did't test MySQL three years, But three years ago, MySQL rollback
> > > was really, really slow.
> >
> > Based on recent testing I did, rollbacks are very expensive -- like 3x to 4x
> > the cost of the original insert in high-concurrency environments. Also not
> > always reliable (as of 5.0).
>
> Wow, that's a serious gotcha. If there's a way to reproduce that we
> should certainly let Ian Barwick of MySQL gotchas fame know about it.
That's under "Epic, feature-length rollbacks," and yes, that's with
InnoDB tables. MyISAM tables have no ROLLBACK capability at all.
http://sql-info.de/en/mysql/transaction-innodb-table.html#4_3
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
phone: +1 415 235 3778 AIM: dfetter666
Skype: davidfetter
Remember to vote!
Consider donating to PostgreSQL: http://www.postgresql.org/about/donate
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2007-08-15 02:13:49 | Re: default_text_search_config and expression indexes |
| Previous Message | Josh Berkus | 2007-08-14 23:47:56 | Re: 12 Silver Bullets |