From: Stewart Smith
Date: January 29 2013 1:05am
Subject: Re: [Maria-developers] what pros/cons of storing binary log in an InnoDB table?
List-Archive: http://lists.mysql.com/internals/38701
Message-Id: <874ni094th.fsf@flamingspork.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"

--=-=-=
Content-Transfer-Encoding: quoted-printable

Kristian Nielsen <knielsen@stripped> writes:
> You will be writing your data *6* times: To the real table, when flushing=
 its
> buffer pool pages. To the double-write buffer while flushing, and to the =
redo
> log before flushing. Then to the binlog table, and before that to the red=
o log
> and the doublewrite buffer. I could never reconcile myself with this.

Mind you, it performs really quite well due to the reduced fsync()s and
(at least in Drizzle code) was rather trivial to implement. Big bang for
buck :)

=2D-=20
Stewart Smith

--=-=-=
Content-Type: application/pgp-signature

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

iQIcBAEBAgAGBQJRByBbAAoJEP08notdpDyv1BUP/Ry3mZESe6TzSFsmIdjjgNW7
yXckABlbBUp4NXQ58lLgVtuiLb+1W9ZEU8UNLnXExaAt3WGCzs6ua8MiRjbT5KQ7
QBTaizz54YnmD/CZbqjO0050aaTBl3dck6JyIlcRNCCzJQFCfSycHRlERw4DUMrw
Hd3T6IQoJKFbO92nykJJ/SNuvPS7sE9k5if7XHpsNR1yRIJxK8yiLDicnbBc6GR5
KQweHUtkvr9OKxwCRKXgP85KWyRWe0m/U1cqmIvP6S7myo+Z2I8jQXgoOib4cwIl
BMp5m9HoFdo3HU+93DPJiS/UEFTahQIDq8KTdegfW6aoMuRFKKwEy6pitSJEZtFj
5BjX0q3tWN54PqRt05C2SrihEB+T/zti5z4ZEdzQXYTW551Bswcka7RQyrpI7aRo
7E13cL8RHJ9L2U+L1ZblNv8rU8BuRYKgu++a2bYeHUwAvrWhi2obQJJrsOWIEJ0l
SEY10QtGDBycjuMR0n98IgaE5jyP7IX0eGzDJLfReaBxCWSyVdOcZ6wBNMkug/pM
KDU6N8oQYTmdhq9nc3GGIXzrG7LCUPdW3hnNLwwSDUTnm0J0OSvfm+Xyt2yIfnZo
koFX38TECEN/dzRqLIqAU53qFAtUTHpsv4O+eIXB8UNJ8Ov+/EbTEosrF+d2JjWe
Mv2KYaKLPOq0KKMf8BRK
=C+G0
-----END PGP SIGNATURE-----
--=-=-=--