diff options
| author | unknown <kaa@polly.(none)> | 2007-10-12 14:03:51 +0400 |
|---|---|---|
| committer | unknown <kaa@polly.(none)> | 2007-10-12 14:03:51 +0400 |
| commit | 65a32e834fe2f5cdf173c40a262c0e85d6fe90e5 (patch) | |
| tree | b1cb0bfa35ca45724b15697013ef95c4d6228d27 /mysys/my_os2dirsrch.h | |
| parent | bc8d42f96dc4760bfa843affb343d6b446355296 (diff) | |
| download | mariadb-git-65a32e834fe2f5cdf173c40a262c0e85d6fe90e5.tar.gz | |
Fix for bug #31254: "Max_data_length" truncated / reported wrong
(compiler issue ?)
Problem:
Improper compile-time flags on AIX prevented use of files > 2 GB. This
resulted in Max_data_length being truncated to 2 GB by MyISAM code.
Solution:
Reverted large-file changes from the fix for bug10776. We need to define
_LARGE_FILES on AIX to have support for files > 2 GB.
Since _LARGE_FILE_API is incompatible with _LARGE_FILES and may be
automatically defined by including standards.h, we also need a
workaround to avoid this conflict.
config/ac-macros/large_file.m4:
Reverted large-file changes from the fix for bug10776. We need to define
_LARGE_FILES on AIX to have support for files > 2 GB.
include/my_global.h:
_LARGE_FILE_API is defined in standards.h that is automatically included
by at least some C++ compilers on AIX. Since it is also incompatible
with _LARGE_FILES which is required for POSIX IO calls to be
largefile-safe, the only workaround is to explicitely #undef
_LARGE_FILE_API.
Diffstat (limited to 'mysys/my_os2dirsrch.h')
0 files changed, 0 insertions, 0 deletions