From: Jeff Smelser
Date: February 14 2005 6:04pm
Subject: Re: Can I dissable transactions?
List-Archive: http://lists.mysql.com/mysql/179914
Message-Id: <200502141204.21120.tradergt@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed;
  boundary="nextPart3518134.PUsquzTg0B";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart3518134.PUsquzTg0B
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Monday 14 February 2005 03:52 am, Ben Clewett wrote:
> I am having a lot of problems deleting a large amount of data.  Say 20GB
> from a 40GB table.  I seem to get failure quite a lot (due NOT to mysql,
> but bad hardware), then MySQL roles back the transaction, which takes as
> many hours and starting the transaction.  I also get this a lot:

There is a feature of DB2 that can do this.. Its really not always all its=
=20
cracked up to be..

In this case, it would happily delete, if something goes wrong, your table =
is=20
now marked bad.. The other 20million rows are now gone.. Is that what you=20
want?

What you need to do, is set up a simple script to delete 20,000 rows a time=
,=20
and commit, just keep doing it till its done.. This way you could do 20,000=
=20
rows, wait a bit, do it again. or whatever. If it fails, you only rollback=
=20
what it was doing during the transaction and you wont have to start all ove=
r.

Jeff

--nextPart3518134.PUsquzTg0B
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQBCEOgloOk9EvUvEtgRAmgKAJ9h+PNNheX+d7PnjaFVqOLGec9PYwCcCmJn
ilKKts2kk4FSMND0pbA+Hbo=
=mkm4
-----END PGP SIGNATURE-----

--nextPart3518134.PUsquzTg0B--