@@ -5772,9 +5772,6 @@ Change sort to allocate memory in ``hunks'' to get better memory utilisation.
5772
5772
@code{Field_decimal::store(const char *from,uint len)} must be recoded
5773
5773
to fix this.
5774
5774
@item
5775
- Fix @code{mysql.cc} to do fewer @code{malloc()} calls when hashing field
5776
- names.
5777
- @item
5778
5775
Functions:
5779
5776
ADD_TO_SET(value,set) and REMOVE_FROM_SET(value,set)
5780
5777
@item
@@ -5809,8 +5806,6 @@ join type.
5809
5806
@item
5810
5807
Oracle like @code{CONNECT BY PRIOR ...} to search hierarchy structures.
5811
5808
@item
5812
- @code{RENAME DATABASE}
5813
- @item
5814
5809
@code{mysqladmin copy database new-database}. -- Requires COPY command to be
5815
5810
added to @code{mysqld}
5816
5811
@item
@@ -24006,7 +24001,7 @@ By default, the @code{mysql.server} script starts the MySQL
24006
24001
server with the @code{-l} option. If you need better performance when
24007
24002
you start using MySQL in a production environment, you can
24008
24003
remove the @code{-l} option from @code{mysql.server} or change it to
24009
- @code{--log-binary }.
24004
+ @code{--log-bin }.
24010
24005
24011
24006
The entries in this log are written as @code{mysqld} receives the questions.
24012
24007
This may be different than the order in which the statements are executed.
@@ -24080,8 +24075,8 @@ and the crash.
24080
24075
@cindex binary log
24081
24076
@cindex files, binary log
24082
24077
24083
- In the future the binary log will replace the update log, so we
24084
- recommend you to switch to this log format as soon as possible!
24078
+ The intention is that the binary log should replace the update log, so
24079
+ we recommend you to switch to this log format as soon as possible!
24085
24080
24086
24081
The binary log contains all information that is available in the update
24087
24082
log in a more efficient format. It also contains information about how long
@@ -24096,6 +24091,14 @@ file name is given, it defaults to the name of the host machine followed
24096
24091
by @code{-bin}. If file name is given, but it doesn't contain a path, the
24097
24092
file is written in the data directory.
24098
24093
24094
+ If you supply an extension to @code{--log-bin=filename.extension}, the
24095
+ extension will be silenty removed.
24096
+
24097
+ To the binary log filename @code{mysqld} will append an extension that is a
24098
+ number that is incremented each time you execute @code{mysqladmin
24099
+ refresh}, execute @code{mysqladmin flush-logs}, execute the @code{FLUSH LOGS}
24100
+ statement or restart the server.
24101
+
24099
24102
You can use the following options to @code{mysqld} to affect what is logged
24100
24103
to the binary log:
24101
24104
@@ -24110,11 +24113,6 @@ Tells the master that updates to the given database should not be logged
24110
24113
to the binary log (Example: @code{binlog-ignore-db=some_database})
24111
24114
@end multitable
24112
24115
24113
- To the binary log filename @code{mysqld} will append an extension that is a
24114
- number that is incremented each time you execute @code{mysqladmin
24115
- refresh}, execute @code{mysqladmin flush-logs}, execute the @code{FLUSH LOGS}
24116
- statement or restart the server.
24117
-
24118
24116
To be able to know which different binary log files have been used,
24119
24117
@code{mysqld} will also create a binary log index file that
24120
24118
contains the name of all used binary log files. By default this has the
@@ -48950,6 +48948,7 @@ users use this code as the rest of the code and because of this we are
48950
48948
not yet 100% confident in this code.
48951
48949
48952
48950
@menu
48951
+ * News-3.23.45:: Changes in release 3.23.45
48953
48952
* News-3.23.44:: Changes in release 3.23.44
48954
48953
* News-3.23.43:: Changes in release 3.23.43
48955
48954
* News-3.23.42:: Changes in release 3.23.42
@@ -48998,10 +48997,42 @@ not yet 100% confident in this code.
48998
48997
* News-3.23.0:: Changes in release 3.23.0
48999
48998
@end menu
49000
48999
49001
- @node News-3.23.44, News-3.23.43, News-3.23.x, News-3.23.x
49000
+ @node News-3.23.45, News-3.23.44, News-3.23.x, News-3.23.x
49001
+ @appendixsubsec Changes in release 3.23.45
49002
+ @itemize @bullet
49003
+ @item
49004
+ Fixed problem with @code{t1 LEFT_JOIN t2 ... WHERE t2.date_column IS NULL} when
49005
+ date_column was declared as @code{NOT NULL}.
49006
+ @item
49007
+ Fixed bug with BDB tables and keys on @code{BLOB}'s.
49008
+ @item
49009
+ Fixed bug in @code{MERGE} tables on OS with 32 bit file pointers.
49010
+ @item
49011
+ Fixed bug in @code{TIME_TO_SEC()} when using negative values.
49012
+ @end itemize
49013
+
49014
+ @node News-3.23.44, News-3.23.43, News-3.23.45, News-3.23.x
49002
49015
@appendixsubsec Changes in release 3.23.44
49003
49016
@itemize @bullet
49004
49017
@item
49018
+ Fixed @code{Rows_examined} count in slow query log.
49019
+ @item
49020
+ Fixed bug when using a reference to a @code{AVG()} column in @code{HAVING}.
49021
+ @item
49022
+ Fixed that date functions that require correct dates, like
49023
+ @code{DAYOFYEAR(column)} will return @code{NULL} for @code{0000-00-00} dates.
49024
+ @item
49025
+ Fixed bug in const-propagation when comparing columns of different
49026
+ types. (@code{SELECT * FROM date_col="2001-01-01" and date_col=time_col})
49027
+ @item
49028
+ Fixed bug that caused error message @code{Can't write, because of unique
49029
+ constraint} with some @code{GROUP BY} queries.
49030
+ @item
49031
+ Fixed problem with sjis character strings used within quoted table names.
49032
+ @item
49033
+ Fixed coredump when using @code{CREATE ... FULLTEXT} keys with other table
49034
+ handlers than MyISAM.
49035
+ @item
49005
49036
Don't use @code{signal()} on windows because this appears to not be
49006
49037
100 % reliable.
49007
49038
@item
@@ -49011,9 +49042,62 @@ that had @code{NULL} values.
49011
49042
Fixed bug when doing @code{LEFT JOIN ... ON (column_name = constant) WHERE column_name = constant}.
49012
49043
@item
49013
49044
When using replications, aborted queries that contained @code{%} could cause
49014
- a core dum.
49045
+ a core dump.
49046
+ @item
49047
+ @code{TCP_NODELAY} was not used on some systems. (Speed problem).
49048
+ @item
49049
+ Applied portability fixes for OS/2 (Patch by Yuri Dario).
49050
+ @end itemize
49051
+
49052
+ The following changes are for @code{InnoDB} tables:
49053
+
49054
+ @itemize @bullet
49055
+ @item
49056
+ Add missing @code{InnoDB} variables to @code{SHOW VARIABLES}.
49057
+ @item
49058
+ Foreign keys checking is now done for @code{InnoDB} tables.
49059
+ @item
49060
+ @code{DROP DATABASE} now works also for @code{InnoDB} tables.
49061
+ @item
49062
+ @code{InnoDB} now supports data files and raw disk partitions bigger
49063
+ than 4 GB on those operating systems which have big files.
49064
+ @item
49065
+ @code{InnoDB} calculates better table cardinality estimates for the
49066
+ MySQL optimizer.
49067
+ @item
49068
+ Accent characters in the default character set latin1 are ordered
49069
+ according to the MySQL ordering.
49070
+
49071
+ NOTE: if you are using latin1 and have inserted characters whose code is >
49072
+ 127 to an indexed CHAR column, you should run CHECK TABLE on your table when
49073
+ you upgrade to 3.23.44, and drop and reimport the table if CHECK TABLE
49074
+ reports an error!
49075
+ @item
49076
+ A new @file{my.cnf} parameter @code{innodb_thread_concurrency} helps in
49077
+ performance tuning in heavily concurrent environments.
49078
+ @item
49079
+ A new @code{my.cnf} parameter @code{innodb_fast_shutdown} speeds up
49080
+ server shutdown.
49081
+ @item
49082
+ A new @code{my.cnf} parameter @code{innodb_force_recovery} helps to save
49083
+ your data in case the disk image of the database becomes corrupt.
49084
+ @item
49085
+ @code{innodb_monitor} has been improved and a new
49086
+ @code{innodb_table_monitor} added.
49087
+ @item
49088
+ Increased maximum key length from 500 to 7000 bytes.
49089
+ @item
49090
+ Fixed a bug in replication of auto-inc columns with multiline inserts.
49091
+ @item
49092
+ Fixed a bug when the case of letters changes in an update of an indexed
49093
+ secondary column.
49094
+ @item
49095
+ Fixed a hang when there are > 24 data files.
49096
+ @item
49097
+ Fixed a crash when @code{MAX(col)} is selected from an empty table, and
49098
+ col is a not the first column in a multi-column index.
49015
49099
@item
49016
- TCP_NODELAY was not used on some systems. (Speed problem) .
49100
+ Fixed a bug in purge which could cause crashes .
49017
49101
@end itemize
49018
49102
49019
49103
@node News-3.23.43, News-3.23.42, News-3.23.44, News-3.23.x
@@ -49117,15 +49201,15 @@ Fixed possible problem with @code{shutdown} on Solaris where the
49117
49201
@item
49118
49202
InnoDB now supports < 4 GB rows. The former limit was 8000 bytes.
49119
49203
@item
49120
- The @code{doublewrite} file flush method is used in InnoDB.
49204
+ The @code{doublewrite} file flush method is used in @code{ InnoDB} .
49121
49205
It reduces the need for Unix fsync calls to a fraction and
49122
49206
improves performance on most Unix flavors.
49123
49207
@item
49124
- You can now use the InnoDB Monitor to print a lot of InnoDB state
49208
+ You can now use the @code{ InnoDB} Monitor to print a lot of @code{ InnoDB} state
49125
49209
information, including locks, to the standard output; useful in
49126
49210
performance tuning.
49127
49211
@item
49128
- Several bugs which could cause hangs in InnoDB have been fixed.
49212
+ Several bugs which could cause hangs in @code{ InnoDB} have been fixed.
49129
49213
@item
49130
49214
Split @code{record_buffer} to @code{record_buffer} and
49131
49215
@code{record_rnd_buffer}. To make things compatible to previous MySQL
@@ -49239,7 +49323,7 @@ Extended argument length in option files from 256 to 512 chars.
49239
49323
Fixed problem with shutdown when @code{INSERT DELAYED} was waiting for
49240
49324
a @code{LOCK TABLE}.
49241
49325
@item
49242
- Fixed coredump bug in InnoDB when tablespace was full.
49326
+ Fixed coredump bug in @code{ InnoDB} when tablespace was full.
49243
49327
@item
49244
49328
Fixed problem with @code{MERGE} tables and big tables (> 4G) when using
49245
49329
@code{ORDER BY}.
@@ -49284,7 +49368,7 @@ New program @code{mysqlcheck}.
49284
49368
Added database name to output for administrative commands like @code{CHECK},
49285
49369
@code{REPAIR}, @code{OPTIMIZE}.
49286
49370
@item
49287
- Lots of portability fixes for InnoDB.
49371
+ Lots of portability fixes for @code{ InnoDB} .
49288
49372
@item
49289
49373
Changed optimiser so that queries like
49290
49374
@code{SELECT * FROM table_name,table_name2 ... ORDER BY key_part1 LIMIT #}
@@ -54880,15 +54964,15 @@ Make a second backup of the tables.
54880
54964
Remove (or move away) any old log files from the MySQL data
54881
54965
directory if you need more space.
54882
54966
@item
54883
- Start @code{mysqld} with @code{--log-binary }. @xref{Binary log}.
54967
+ Start @code{mysqld} with @code{--log-bin }. @xref{Binary log}.
54884
54968
If you want to find a query that crashes @code{mysqld}, you should use
54885
- @code{--log --log-binary }.
54969
+ @code{--log --log-bin }.
54886
54970
@item
54887
54971
When you have gotten a crashed table, stop the @code{mysqld server}.
54888
54972
@item
54889
54973
Restore the backup.
54890
54974
@item
54891
- Restart the @code{mysqld} server @strong{without} @code{--log-binary }
54975
+ Restart the @code{mysqld} server @strong{without} @code{--log-bin }
54892
54976
@item
54893
54977
Re-execute the commands with @code{mysqlbinlog update-log-file | mysql}.
54894
54978
The update log is saved in the MySQL database directory with
0 commit comments