-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
On Fri, 23 Jul 2004, Christian Hammers wrote:
> On Fri, 23 Jul 2004 01:33:35 +0200 (CEST)
>
> > Another option that might be worth enabling is "-DBIG_TABLES" - that
>
> Is this up-to-date? mysqld compiled without this option prints
> "--big-tables" as option and happily starts with it. At least, if it
> takes this option but then ignores it, this would be a bug :-)
No, this is actually a different thing :)
According to the manual:
Allow large result sets by saving all temporary sets in files. This
option prevents most ``table full'' errors, but also slows down queries
for which in-memory tables would suffice. Since MySQL 3.23.2, the
server is able to handle large result sets automatically by using memory
for small temporary tables and switching to disk tables where necessary.
The compile option increases the maximum number of Rows per table:
#if SIZEOF_OFF_T > 4 && defined(BIG_TABLES)
#define GET_HA_ROWS GET_ULL
#else
#define GET_HA_ROWS GET_ULONG
#endif
Bye,
LenZ
- --
Lenz Grimmer <lenz@stripped>
Senior Production Engineer
MySQL GmbH, http://www.mysql.de/
Hamburg, Germany
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/
iD8DBQFBBhA/SVDhKrJykfIRAq11AJ9Wx7dn2tP8sgOicb6Xyx4GtHTI+ACeKvHr
t+XA16WwvLYlLg0gE+ZYhNs=
=oNn2
-----END PGP SIGNATURE-----
