At least the following options should be different per server:
@table @code
@item port=#
@item socket=path
@item pid-file=path
@end table
The following options should be different, if they are used:
@table @code
@item log=path
@item log-bin=path
@item log-update=path
@item log-isam=path
@item bdb-logdir=path
@end table
If you want more performance, you can also specify the following differently:
@table @code
@item tmpdir=path
@item bdb-tmpdir=path
@end table
@xref{Command-line options}.
If you are installing binary @strong{MySQL} versions (.tar files) and
start them with @code{./bin/safe_mysqld} then in most cases the only
option you need to add/change is the @code{socket} and @code{port}
argument to @code{safe_mysqld}.
@node Upgrade, , Installing many servers, Installing
@section Upgrading/Downgrading MySQL
@cindex upgrading
@cindex downgrading
...
...
@@ -9826,7 +9886,11 @@ all your tables with @code{isamchk -r}, as we have made some changes in
the sort order!
@item The default return type of @code{IF} will now depend on both arguments
and not only the first argument.
@item @code{AUTO_INCREMENT} will not work with negative numbers.
@item @code{AUTO_INCREMENT} will not work with negative numbers. The reason
for this is that negative numbers caused problems when wrapping from -1 to 0.
@code{AUTO_INCREMENT} is now for MyISAM tables handled at a lower level and
is much faster than before. For MyISAM tables old numbers are also not reused
anymore, even if you delete some rows from the table.
@item @code{INNER}, @code{DELAYED}, @code{RIGHT}, @code{CASE}, @code{THEN}, @code{WHEN}, @code{ELSE}, @code{END} and @code{WHEN} are now reserved words.
@item @code{FLOAT(X)} is now a true floating-point type and not a value with
a fixed number of decimals.
...
...
@@ -40354,7 +40418,7 @@ get more locking options.
@end itemize
@node News-3.23.x, News-3.22.x, News-4.0.x, News
@appendixsec Changes in release 3.23.x (Recommended; Gamma)
@appendixsec Changes in release 3.23.x (Recommended)
The 3.23 release has several major new features that are not
present in the 3.22 or 3.21 releases. We have added two new
...
...
@@ -40364,12 +40428,23 @@ DB library from Sleepycat Software to implement transaction-safe
tables. The 3.23 release also includes support for database
replication between a master and many slaves.
We are not adding any more new features that are likely to break any
old code in @strong{MySQL} Version 3.23, so we recommend that you use this
version. The replication and BerkeleyDB code is still under development,
though, so Version 3.23 is not released as a stable version yet.
We are in the future aiming to only provide bug fixes for 3.23 and
instead concentrate on the 4.0 version.
The replication code and BerkeleyDB code is still not as tested and as
the rest of the code, so we will probably need to do a couple of future
releases of 3.23 with small fixes for this part of the code. As long as
you don't use these features, you should be quite safe with
@strong{MySQL} 3.23!
Note that the above doesn't mean that replication or Berkeley DB doesn't
work; We have done a lot of testing of all code, including replication
and BDB without finding any problems. It only means that not as many
users uses this code as the rest of the code and because of this we are
not yet 100 % confident in this code.
@menu
* News-3.23.32::
* News-3.23.31:: Changes in release 3.23.31
* News-3.23.30:: Changes in release 3.23.30
* News-3.23.29:: Changes in release 3.23.29
...
...
@@ -40404,7 +40479,18 @@ though, so Version 3.23 is not released as a stable version yet.
for i in libmysql/.libs/libmysqlclient.a libmysql/.libs/libmysqlclient.so* libmysql/libmysqlclient.* libmysql_r/.libs/libmysqlclient_r.a libmysql_r/.libs/libmysqlclient_r.so* libmysql_r/libmysqlclient_r.* mysys/libmysys.a strings/libmystrings.a dbug/libdbug.a $BASE/lib
