| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
configure.in.rej
include/my_global.h.rej
BUILD/SETUP.sh.rej
mysys/thr_alarm.c.rej
include/my_pthread.h.rej
|
|\
| |
| |
| | |
into mysql.com:/home/kent/bk/tmp/mysql-4.1-build
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Removed unused files
.del-my_winsem.c:
Delete: mysys/my_winsem.c
.del-my_semaphore.c:
Delete: mysys/my_semaphore.c
.del-my_semaphore.h:
Delete: include/my_semaphore.h
|
| |
| |
| |
| |
| |
| |
| | |
Companion change to this one
ChangeSet@1.2206, 2007-01-22 02:32:07+02:00, jani@a88-113-38-195.elisa-laajakaista.fi +8 -0
include/my_pthread.h@1.67, 2007-01-22 02:32:06+02:00, jani@a88-113-38-195.elisa-laajakaista.fi +31 -10
which renamed "sigset()" -> "my_sigset()" but forgot to do it for Windows ...
|
| | |
|
|\ \
| |/
| |
| | |
into chilla.local:/home/mydev/mysql-4.1-axmrg
|
| |\
| | |
| | |
| | | |
into production.mysql.com:/usersnfs/jamppa/mysql-4.0
|
| | |
| | |
| | |
| | |
| | | |
Move get_thread_lib to mysys/my_pthread.c
Set 'thr_client_alarm' to signal number used by thr_alarm to give alarms
|
| |/
| |
| |
| |
| |
| | |
Move get_thread_lib to mysys/my_pthread.c
Set 'thr_client_alarm' to signal number used by thr_alarm to give alarms
|
|\ \
| |/
| |
| | |
into a88-113-38-195.elisa-laajakaista.fi:/home/my/bk/mysql-4.1
|
| |
| |
| |
| |
| | |
Fix to check library in use during runtime.
Fix for Bug#16995, "idle connections not being killed due to timeout when NPTL is used".
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
(back-port to 4.0)
Socket timeouts in client library were used only on Windows.
Additionally, in 4.0 write operations erroneously set read timeout.
The solution is to use socket timeouts in client library on all
systems were they are supported, and to differentiate between read
and write timeouts.
No test case is provided because it is impossible to simulate network
failure in current test suite.
|
| |
| |
| |
| |
| |
| |
| |
| | |
subject of "concurrent insert""
The previous bug fix didn't work when using partial keys.
Don't use GNUC min/max operations are they are depricated.
Fixed valgrind warning
|
| |
| |
| |
| | |
Patch from Alfredo for TARGET_FAT_BINARY
|
|\ \
| | |
| | |
| | | |
into neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint
|
| | | |
|
| |\ \
| | | |
| | | |
| | | | |
into mysql.com:/home/hf/work/mysql-4.1-mrg
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
the incompatibility was caused by current_stmt member added to the MYSQL
structure.
It's possible to move it to THD structure instead which saves ABI
|
|\ \ \ \
| |/ / /
| | | |
| | | | |
into neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint
|
| |\ \ \
| | | | |
| | | | |
| | | | | |
into outpost.site:/home/cps/mysql/trees/4.1-runtime-bug9191
|
| | |\ \ \
| | | |/ /
| | |/| |
| | | | | |
into outpost.site:/home/cps/mysql/trees/4.1-runtime-bug9191
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
(4.1 version, with post-review fixes)
The fix for another Bug (6439) limited FROM_UNIXTIME() to
TIMESTAMP_MAX_VALUE which is 2145916799 or 2037-12-01 23:59:59 GMT,
however unix timestamp in general is not considered to be limited
by this value. All dates up to power(2,31)-1 are valid.
This patch extends allowed TIMESTAMP range so, that max
TIMESTAMP value is power(2,31)-1. It also corrects
FROM_UNIXTIME() and UNIX_TIMESTAMP() functions, so that
max allowed UNIX_TIMESTAMP() is power(2,31)-1. FROM_UNIXTIME()
is fixed accordingly to allow conversion of dates up to
2038-01-19 03:14:07 UTC. The patch also fixes CONVERT_TZ()
function to allow extended range of dates.
The main problem solved in the patch is possible overflows
of variables, used in broken-time representation to time_t
conversion (required for UNIX_TIMESTAMP).
|
| | | | | |
|
|/ / / /
| | | |
| | | |
| | | | |
to pass the directory to use. I.e --mem=<directory>
|
|\ \ \ \
| |/ / /
|/| | |
| | | | |
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-4.1-maint
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
BUG#23427 incompatible ABI change in 5.0.26?
- Use the icheck tool if avaliable and compare the current mysql.h to a version
controlled reference file
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This will hopefully avoiid annoying crashes when running with --debug
Fix warnings from the above in mysqltest.c
|
| |\ \ \
| | | | |
| | | | |
| | | | | |
into polly.local:/home/kaa/src/maint/m41-maint--07OGk
|
| | |\ \ \
| | | | | |
| | | | | |
| | | | | | |
into polly.local:/home/kaa/src/maint/m41-maint--07OGk
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
- bug #11655 "Wrong time is returning from nested selects - maximum time exists
- input and output TIME values were not validated properly in several conversion functions
- bug #20927 "sec_to_time treats big unsigned as signed"
- integer overflows were not checked in several functions. As a result, input values like 2^32 or 3600*2^32 were treated as 0
- BIGINT UNSIGNED values were treated as SIGNED in several functions
- in cases where both input string truncation and out-of-range TIME value occur, only 'truncated incorrect time value' warning was produced
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | | |
into chilla.local:/home/mydev/mysql-4.1-bug8283-one
|
| |\ \ \ \ \ \
| | |_|_|_|/ /
| |/| | | | |
| | | | | | | |
into chilla.local:/home/mydev/mysql-4.1-bug8283-one
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
OPTIMIZE TABLE with myisam_repair_threads > 1 performs a non-quick
parallel repair. This means that it does not only rebuild all
indexes, but also the data file.
Non-quick parallel repair works so that there is one thread per
index. The first of the threads rebuilds also the new data file.
The problem was that all threads shared the read io cache on the
old data file. If there were holes (deleted records) in the table,
the first thread skipped them, writing only contiguous, non-deleted
records to the new data file. Then it built the new index so that
its entries pointed to the correct record positions. But the other
threads didn't know the new record positions, but put the positions
from the old data file into the index.
The new design is so that there is a shared io cache which is filled
by the first thread (the data file writer) with the new contiguous
records and read by the other threads. Now they know the new record
positions.
Another problem was that for the parallel repair of compressed
tables a common bit_buff and rec_buff was used. I changed it so
that thread specific buffers are used for parallel repair.
A similar problem existed for checksum calculation. I made this
multi-thread safe too.
|
| | |_|/ / /
| |/| | | | |
|
|\ \ \ \ \ \
| | |_|/ / /
| |/| | | |
| | | | | | |
into mysql.com:/home/gluh/MySQL/Merge/4.1-kt
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
function pointers
This was available from gcc 3.1, so diable it before that
Update m_ctype.h to use the new macro
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
doesn't support full GNU syntax
- disable __attribute__ when using qcc
|
| | | | | | |
|
| | | | | | |
|
| | |_|/ /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fix when __attribute__() is stubbed out, add ATTRIBUTE_FORMAT() for specifying
__attribute__((format(...))) safely, make more use of the format attribute,
and fix some of the warnings that this turns up (plus a bonus unrelated one).
|
| | | | |
| | | | |
| | | | |
| | | | | |
patch)
|
|\ \ \ \ \
| | |/ / /
| |/| | |
| | | | | |
into mysql.com:/usr/home/bar/mysql-4.1.b20471v2
|
| |/ / /
| | | |
| | | |
| | | | |
Bug#21432 Database/Table name limited to 64 bytes, not chars, problems with multi-byte
|
|/ / /
| | |
| | |
| | |
| | | |
The main problem was already fixed by Igor under terms of 16674.
Adding some additional minor fixes and tests.
|
|\ \ \
| | | |
| | | |
| | | | |
into mysql.com:/home/hf/work/mysql-4.1.16017
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
There actually was 3 different problems -
hash_user_connections wasn't cleaned
one strdupped database name wasn't freed
and stmt->mem_root wasn't cleaned as it was
replased with mysql->field_alloc for result
For the last one - i made the library using stmt's
fields to store result if it's the case.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
hp_test2 now works again
Fixed wrong cast, which caused problems with gcc 4.0 and floats in prepared statements (Bug #19694)
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
there was two problems about charsets in embedded server
1. mysys/charset.c - defined there default_charset_info variable is
modified by both server and client code (particularly when
--default-charset option is handled)
In embedded server we get two codelines modifying one variable.
I created separate default_client_charset_info for client code
2. mysql->charset and mysql->options.charset initialization isn't
properly done for embedded server - necessary calls added
|
|/ /
| |
| |
| | |
refers to a column name.
|