From: Reindl Harald
Date: November 29 2011 10:19pm
Subject: Re: help needed restoring crashed mysql
List-Archive: http://lists.mysql.com/mysql/226387
Message-Id: <4ED55A56.50304@thelounge.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enig7BCF65463A1690968121FA7F"

--------------enig7BCF65463A1690968121FA7F
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



Am 29.11.2011 20:25, schrieb Karen Abgarian:
>=20
> On 29.11.2011, at 5:21, Reindl Harald wrote:
>> why is this dumb "innodb_file_per_table=3D0" default since MOST PEOPLE=

>> have only troubles with it because they can not free space with
>> "optimize table" with no real benefits?
>
> The logic behind this is probably that without innodb_file_per_table=3D=
1
> and with several large ibdata files, the space IS freed up when one doe=
s
> optimize table or drop table.  The space is freed up inside the databas=
e
> files and can be reused. =20

well, and if you have this day 2 TB mysql-data and a year later
get rid of 1 TB of it they allocated space can be REUSED for
innodb but never for any other application

> If we think about it, the database product should only resolve problems=
 of
> the database space management, not of the OS space management.=20

the database producht with default settings is the part starting
the troubles of os-space-managment and this is idiotic, no other
words for this!

MY only luck is that i recognized this years ago after PLAYING
with innodb and so i started with "innodb_file_per_table=3D1" from
the begin with the first production database

> the user essentially asked InnoDB to keep allocating arbitrary amount o=
f space
> as needed, ignoring that the OS disk is actually of the limited size.  =
To be
> correct about it, the user should have stated that the ibdata file shou=
ld have a
> firm limit and not autoextend beyond that.=20

yes this case is a user-problem

but the cases where ibdata1 is growing becasue ONCE bigger
data was stored and never release the allocated space is a
design-problem


--------------enig7BCF65463A1690968121FA7F
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk7VWlYACgkQhmBjz394AnkB9gCfeqSLOSZLzfSle+JZJOJWjtmY
IHsAoJHhOmRmdKaDo3M1/QJ0rnV+Jh+X
=xW+t
-----END PGP SIGNATURE-----

--------------enig7BCF65463A1690968121FA7F--