| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| | |
into bodhi.local:/opt/local/work/mysql-5.1-runtime
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Cache".
WL#1569 "Prepared Statements: implement support of Query Cache".
Prepared SELECTs did not look up in the query cache, and their results
were not stored in the query cache. This made them slower than
non-prepared SELECTs in some cases.
The fix is to re-use the expanded query (the prepared query where
"?" placeholders are replaced by their values, at execution time)
for searching/storing in the query cache.
It works fine for statements prepared via mysql_stmt_prepare(), which
are the most commonly used and were the scope of this bugfix and WL.
It works less fine for statements prepared via the SQL command
PREPARE...FROM, which are still not using the query cache if they
have at least one parameter (because then the expanded query contains
names of user variables, and user variables don't work with the
query cache, even in non-prepared queries).
Note that results from prepared SELECTs, which are in the binary
protocol, and results from normal SELECTs, which are in the text
protocol, ignore each other in the query cache, because a result in the
binary protocol should never be served to a SELECT expecting the text
protocol and vice-versa.
Note, after this patch, bug 25843 starts applying to query cache
("changing default database between PREPARE and EXECUTE of statement
breaks binlog"), we need to fix it.
|
| |\ \
| |/
|/|
| | |
into pilot.mysql.com:/home/msvensson/mysql/mysql-5.1-new-maint
|
| | |
| |
| |
| |
| |
| |
| | |
- Implement --secure-file-priv=<dir> option that limits
"load_file", "LOAD DATA" and "SELECT .. INTO OUTFILE" to work
with files in specified dir.
- Use above option for mysqld in mysql-test-run.pl
|
| |\ \
| | |
| | |
| | | |
into shellback.(none):/home/msvensson/mysql/mysql-5.1-maint
|
| | |\ \
| | |/
| | |
| | | |
into mysql.com:/home/hf/work/mysql-5.1-mrg
|
| | | |\
| | | |
| | | |
| | | | |
into mysql.com:/home/hf/work/mysql-5.0-0mrg
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The regression is caused by the fix for bug 14767. When INSERT ... SELECT
used a view in the SELECT list that was not inlined, and there was an
active transaction, the server could crash in Query_cache::invalidate.
On INSERT ... SELECT only the table being inserted into is invalidated.
Thus views that can't be inlined are skipped from invalidation.
The bug manifests itself in two ways so there is 2 test cases.
One checks that the only the table being inserted into is invalidated.
And the second one checks that there is no crash on INSERT ... SELECT.
|
| | | |\ \
| | | |/
| | |/|
| | | | |
into neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint
|
| | | | |
| | | |
| | | |
| | | | |
detects problems with test files
|
| |/ / /
| | |
| | |
| | |
| | | |
Fix tests for new behaviour: an error is thrown if a NON DETERMINISTIC
stored function (SF) is called during statement-based replication (SBR).
|
| |\ \ \
| | | |
| | | |
| | | | |
into shellback.(none):/home/msvensson/mysql/same_tools/my51-same_tools
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | |/ /
| |/| |
| | | | |
into dl145s.mysql.com:/data/bk/team_tree_merge/MERGE/mysql-5.1
|
| | | |/
| |/| |
|
| |\ \ \
| |/ /
| | |
| | | |
into maint2.mysql.com:/data/localhome/tsmith/bk/mrg50/51
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
when a range condition use an invalid DATETIME constant.
Now we do not use invalid DATETIME constants to form end keys for
range intervals: range analysis just ignores predicates with such
constants.
|
| |\ \ \
| |_|/
|/| |
| | | |
into sunlight.local:/local_work/tmp_merge-5.1-opt-mysql
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Make the range-et-al optimizer produce E(#table records after table
condition is applied),
- Make the join optimizer use this value,
- Add "filtered" column to EXPLAIN EXTENDED to show
fraction of records left after table condition is applied
- Adjust test results, add comments
|
| |\ \ \
| |/ /
|/| /
| |/ |
into bodhi.local:/opt/local/work/mysql-5.1-runtime-merge-5.0
|
| | |
| |
| |
| |
| |
| |
| |
| | |
The problem was that we restored SQL_CACHE, SQL_NO_CACHE flags in SELECT
statement from internal structures based on value set later at runtime, not
the original value set by the user.
The solution is to remember that original value.
|
| | |
| |
| |
| | |
(Needed for "list of pushes" web page and autopush)
|
| | |
| |
| |
| | |
different vardir.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
com_show_status). Global status variables are still updated.
SHOW STATUS are not anymore put in slow query log because of no index usage.
Implemntation done by removing orig_sql_command and moving logic of SHOW STATUS to mysql_excute_command()
This simplifies code and allows us to remove some if statements all over the code.
Upgraded uc_update_queries[] to sql_command_flags and added more bitmaps to better categorize commands.
This allowed some overall simplifaction when testing sql_command.
Fixes bugs:
Bug#10210: running SHOW STATUS increments counters it shouldn't
Bug#19764: SHOW commands end up in the slow log as table scans
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | | |
neptunus.(none):/home/msvensson/mysql/mysqltestrun_check_testcases/my51-mysqltestrun_check_testcases
into neptunus.(none):/home/msvensson/mysql/mysql-5.1-new
|
| | |\ \
| | | |
| | | |
| | | |
| | | |
| | | | |
neptunus.(none):/home/msvensson/mysql/mysqltestrun_check_testcases/my50-mysqltestrun_check_testcases
into neptunus.(none):/home/msvensson/mysql/mysqltestrun_check_testcases/my51-mysqltestrun_check_testcases
|
| | | |/
| | |
| | |
| | | |
Cleanup the sideeffects from most of the testcases with sideeffects.
|
| | | | |
|
| | | |\
| | | |
| | | |
| | | | |
into sanja.is.com.ua:/home/bell/mysql/bk/work-merge1-5.0
|
| |/ / / |
|
| |\ \ \
| | | |
| | | |
| | | | |
into moonbone.local:/work/15028-bug-5.1-new-mysql
|
| | | | |
| | | |
| | | |
| | | | |
After merge fix
|
| | |\ \ \
| | |/ /
| |/| /
| | |/ |
|
| | | |
| | |
| | |
| | | |
to be in the query cache. (BUG#14652)
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The table opening process now works the following way:
- Create common TABLE_SHARE object
- Read the .frm file and unpack it into the TABLE_SHARE object
- Create a TABLE object based on the information in the TABLE_SHARE
object and open a handler to the table object
Other noteworthy changes:
- In TABLE_SHARE the most common strings are now LEX_STRING's
- Better error message when table is not found
- Variable table_cache is now renamed 'table_open_cache'
- New variable 'table_definition_cache' that is the number of table defintions that will be cached
- strxnmov() calls are now fixed to avoid overflows
- strxnmov() will now always add one end \0 to result
- engine objects are now created with a TABLE_SHARE object instead of a TABLE object.
- After creating a field object one must call field->init(table) before using it
- For a busy system this change will give you:
- Less memory usage for table object
- Faster opening of tables (if it's has been in use or is in table definition cache)
- Allow you to cache many table definitions objects
- Faster drop of table
|
| |\ \
| | |
| | |
| | | |
into mysql.com:/usr/home/ram/work/5.0.b10303
|
| | | |
| | |
| | |
| | |
| | | |
- Packets out of order when reading cached data stored by a normal select from a ps or vice versa.
- Add pkt_nr to query cache flags
|
| |/ / |
|
| | | |
|
| | | |
|
| |\ \
| |/
| |
| | |
into mysql.com:/home/jimw/my/mysql-5.0-clean
|
| | | |
|
| |\ \
| |/
| |
| | |
into deer.(none):/home/hf/work/mysql-5.0.clean
|
| | |
| |
| |
| | |
notembedded-specific part moved to the new test
|
| | | |
|
| |\ \
| | |
| | |
| | | |
into sanja.is.com.ua:/home/bell/mysql/bk/work-bug1-5.0
|
| | | | |
|
| | | | |
|
