From: | Harald Fuchs <nospam(at)sap(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Humor me: Postgresql vs. MySql (esp. licensing) |
Date: | 2003-10-09 11:28:29 |
Message-ID: | pu65iyveea.fsf@srv.protecting.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
In article <20031009030518(dot)GD8265(at)dcc(dot)uchile(dot)cl>,
Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> writes:
> It was not clear to me from the article that originally mentioned it
> that it had an uncommitted transaction, though it may very well be the
> case.
Sridhar mentioned MyISAM tables - thus no transactions at all.
> But given that ROLLBACK takes some unreasonable amount of time in MySQL,
> what do you really expect? Did the rollback work when the poweroff was
> requested? Or did it work only halfway, rendering the whole
> "transaction" model useless?
Been there, done that. You can kill the MySQL server when it's
rolling back a huge transaction. When you restart it, it just
continues the rollback.
From | Date | Subject | |
---|---|---|---|
Next Message | Harald Fuchs | 2003-10-09 11:33:39 | Re: Humor me: Postgresql vs. MySql (esp. licensing) |
Previous Message | Agostinho Sousa | 2003-10-09 10:22:37 | Re: help with large objects in 7.3.4 |