Merge paul@work.mysql.com:/home/bk/mysql

PENDING/2000-10-11.05

PENDING/2000-10-11.06

BitKeeper/etc/csets-out

BitKeeper/etc/csets-in

support-files/mysql-3.23.26-beta.spec

monty@donna.mysql.com

mwagner@evoq.home.mwagner.org

paul@central.snake.net

sasha@mysql.sashanet.com

serg@serg.mysql.com

paul@central.snake.net

# Untar a MySQL distribution, change the copyright texts,

# pack it up again to a given directory

$VER="1.1";

$VER="1.2";

use Getopt::Long;

$opt_help    = 0;

$opt_version = 0;

$opt_target  = "mysql-copyright-target-";

$opt_target .= `date +%d%m%y-%H%M%S`;

chop $opt_target;

GetOptions("help","target=s") || usage();

GetOptions("help","version","target=s") || error();

# fix the directory prefix for target dir

  my $REG_VERSION = '[0-9\.\-]+[a-z]?[0-9\.\-]+?(.alpha|.beta|.gamma|pre\d|[0-9\.\-a-z])?';

  my $target;

  usage() if (!$ARGV[0] || $opt_help);

  if ($opt_version)

  {

    print "$0 version $VER by Jani Tolonen\n";

    exit(0);

  }

  usage() if ($opt_help);

  print error() if ($#ARGV == -1);

  `mkdir -p $opt_target`;

  $pec= $? >> 8;

EOF

  exit(0);

}

####

#### error

####

sub error

{

  if ($#ARGV == -1)

  {

    print "Too few arguments to $0!\n";

  }

  exit(1);

}

../MIRRORS:		manual.texi $(srcdir)/Support/generate-mirror-listing.pl

	perl -w $(srcdir)/Support/generate-mirror-listing.pl manual.texi > $@

# Don't update the files from bitkeeper

%::SCCS/s.%

MySQL table types

* MyISAM::                      MyISAM tables

* MERGE::

* MERGE::                       MERGE tables

* ISAM::                        ISAM tables

* HEAP::                        HEAP tables

* BDB::                         BDB or Berkeley_db tables

Changes in release 3.23.x  (Recommended; beta)

* News-3.23.28::                

* News-3.23.27::                Changes in release 3.23.27

* News-3.23.26::                Changes in release 3.23.26

* News-3.23.25::                Changes in release 3.23.25

* News-3.23.24::                Changes in release 3.23.24

* News-3.23.4::                 Changes in release 3.23.4

* News-3.23.3::                 Changes in release 3.23.3

* News-3.23.2::                 Changes in release 3.23.2

* News-3.23.1::

* News-3.23.1::                 Changes in release 3.23.1

* News-3.23.0::                 Changes in release 3.23.0

Changes in release 3.22.x

Building in a non-source directory is not supported when using

MIT-pthreads, because we want to minimize our changes to this code.

@item

MIT-pthreads doesn't support the @code{AF_UNIX} protocol used to implement

UNIX sockets.  This means that if you compile using MIT-pthreads, all

connections must be made using TCP/IP (which is a little slower).  If you

find after building @strong{MySQL} that you cannot connect to the local

server, it may be that your client is attempting to connect to

@code{localhost} using a UNIX socket as the default. Try making a TCP/IP

connection with @code{mysql} by using a host option (@code{-h} or

@code{--host}) to specify the local host name explicitly.

@item

The checks that determine whether or not to use MIT-pthreads occur only

during the part of the configuration process that deals with the server

For HPUX Version 11.x we recommend @strong{MySQL} 3.23.15 or later.

If you are using @code{gcc} 2.95.1 on a unpatched HPUX Versiib 11.x system,

If you are using @code{gcc} 2.95.1 on a unpatched HPUX 11.x system,

you will get the error:

@example

@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{INNER} and @code{DELAYED} are now reserved words.

@item @code{INNER}, @code{DELAYED}, @code{RIGHT} 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.

@item When declaring @code{DECIMAL(length,dec)} the length argument no

@section @code{REPAIR TABLE} syntax

@example

REPAIR TABLE tbl_name[,tbl_name...] [QUICK]

REPAIR TABLE tbl_name[,tbl_name...] [QUICK] [EXTENDED]

@end example

@code{REPAIR TABLE} only works on @code{MyISAM} tables and is the same things

If @code{QUICK} is given then @strong{MySQL} will try to do a

@code{REPAIR} of only the index tree.

If you use @code{EXTENDED} then @strong{MySQL} will create the index row

by row instead of creating one index at a time with sorting;  This may be

better than sorting on fixed length keys if you have long @code{char()}

keys that compress very good.

@findex DELETE

@node DELETE, SELECT, REPAIR TABLE, Reference

@section @code{DELETE} syntax

If you don't use @code{BDB} tables, you should set this to 0 or

start @code{mysqld} with @code{--skip-bdb} o not waste memory for this cache.

@item @code{bdb_lock_max}

The maximum number of locks (1000 by default) you can have active on a BDB

table. You should increase this if you get errors of type

@code{bdb: Lock table is out of available locks} when you have do long

transactions or when mysqld has to examine a lot of rows to calculate

the query.

@item @code{concurrent_inserts}

If @code{ON} (the default), @strong{MySQL} will allow you to use @code{INSERT}

on @code{MyISAM} tables at the same time as you run @code{SELECT} queries

After this many write locks, allow some read locks to run in between.

@item @code{myisam_sort_buffer_size}

The buffer that is allocated when sorting the index when doing a @code{REPAIR}

table.

The buffer that is allocated when sorting the index when doing a

@code{REPAIR} or when creating indexes with @code{CREATE INDEX} or

@code{ALTER TABLE}.

@item @code{net_buffer_length}

The communication buffer is reset to this size between queries. This

@code{FLUSH TABLES} a lot (which just forces all tables to be closed and

reopenend), then you should increase the value of this variable.

Make sure that your operating system can handle the number of open file

descriptors implied by the @code{table_cache} setting.  If @code{table_cache}

is set too high, @strong{MySQL} may run out of file descriptors and refuse

connections, fail to perform queries, and be very unreliable.

For information about how the table cache works, see @ref{Table cache}.

@item @code{thread_cache_size}

type of error with little disk requirements..

@end itemize

If the recover wouldn't be able to recover all rows from a previous

completed statement and you didn't specify @code{FORCE} as an option to

@code{myisam-recover}, then the automatic repair will abort with an error

message in the error file:

@example

Error: Couldn't repair table: test.g00pages

@end example

If you in this case had used the @code{FORCE} option you would instead have got

a warning in the error file:

@example

Warning: Found 344 of 354 rows when repairing ./test/g00pages

@end example

Note that if you run automatic recover with the @code{BACKUP} option,

you should have a cron script that automaticly moves file with names

like @file{tablename-datetime.BAK} from the database directories to a

@multitable @columnfractions .5 .5

@item @strong{Operating System} @tab @strong{File Size Limit}

@item Linux-Intel @tab 2G (or 4G with reiserfs)

@item Linux-Intel 32 bit@tab 2G, 4G or bigger depending on Linux version

@item Linux-Alpha @tab 8T (?)

@item Solaris 2.5.1 @tab 2G (possible 4G with patch)

@item Solaris 2.6 @tab 4G

@item Solaris 2.7 ULTRA-SPARC @tab 8T (?)

@end multitable

On Linux 2.2 you can get bigger tables than 2G by using the LFS patch for

the ext2 file system.  On Linux 2.4 there exists also patches for ReiserFS

to get support for big files.

This means that the table size for @strong{MySQL} is normally limited by

the operating system.

parameter when you create your table.  @xref{CREATE TABLE}.  You can

also set these later with @code{ALTER TABLE}. @xref{ALTER TABLE}.

If you need to have bigger tables than 2G / 4G

If your big table is going to be read-only, you could use

@code{myisampack} to merge and compress many tables to one.

@code{myisampack} usually compresses a table by at least 50%, so you can

have, in effect, much bigger tables.  @xref{myisampack, ,

@code{myisampack}}.

You can go around the operating system file limit for @code{MyISAM} data

files by using the @code{RAID} option. @xref{CREATE TABLE}.

Another solution can be the included MERGE library, which allows you to

handle a collection of identical tables as one. @xref{MERGE, MERGE

tables}.

really nice) or Linux (because the 2.2 kernel has really good SMP

support). Also on 32bit machines Linux has a 2G file size limit by

default. Hopefully this will be fixed soon when new filesystems is

released (XFS/Reiserfs).

released (XFS/Reiserfs).  If you have a desperate need for files bigger

tan 2G on Linux-intel 32 bit, you should get the LFS patch for the ext2

file system.

Because we have not run @strong{MySQL} in production on that many platforms we

advice you to test your intended platform before choosing it, if possible.

* myisamchk other options::     

@end menu

Note that if you get an error like:

@example

myisamchk: warning: 1 clients is using or hasn't closed the table properly

@end example

This means that you are trying to check a table that has been updated by

the another program (like the mysqld server) that hasn't yet closed

the file or that has died without closing the file properly.

If you @code{mysqld} is running, you must force a sync/close of all

tables with @code{FLUSH TABLES} and ensure that no one is using the

tables while you are running @code{myisamchk}.  In MySQL 3.23 the easiest

way to avoid this problem is to use @code{CHECK TABLE} instead of

@code{myisamchk} to check tables.

@cindex options, @code{myisamchk}

@cindex @code{myisamchk}, options

@node myisamchk general options, myisamchk check options, myisamchk syntax, myisamchk syntax

of connections and their status.

@item

Run the command @code{mysqladmin -i 5 status}

in a separate window to produce statistics while you run your other queries.

Run the command @code{mysqladmin -i 5 status} or @code{mysqladmin -i 5

-r status} or in a separate window to produce statistics while you run

your other queries.

@item

Try the following:

the error code for the most recently invoked API function that can succeed

or fail.  A return value of zero means that no error occurred. Client error

message numbers are listed in the @strong{MySQL} @file{errmsg.h} header file.

Server error message numbers are listed in @file{mysqld_error.h}

Server error message numbers are listed in @file{mysqld_error.h}. In the

@strong{MySQL} source distribution you can find a complete list of

error messages and error numbers in the file @file{Docs/mysqld_error.txt}.

@subsubheading Return values:

though, so 3.23 is not released as a stable version yet.

@menu

* News-3.23.28::                Changes in release 3.23.28

* News-3.23.27::                Changes in release 3.23.27

* News-3.23.26::                Changes in release 3.23.26

* News-3.23.25::                Changes in release 3.23.25

* News-3.23.24::                Changes in release 3.23.24

* News-3.23.0::                 Changes in release 3.23.0

@end menu

@node News-3.23.26, News-3.23.25, News-3.23.x, News-3.23.x

@node News-3.23.28, News-3.23.27, News-3.23.x, News-3.23.x

@appendixsubsec Changes in release 3.23.28

@itemize @bullet

@item

Fixed bug in a BDB key compare function when comparing part keys.

@item

Added variable @code{bdb_lock_max} to @code{mysqld}.

@end itemize

@node News-3.23.27, News-3.23.26, News-3.23.28, News-3.23.x

@appendixsubsec Changes in release 3.23.27

@itemize @bullet

@item

Fixed bug where the automatic repair of MyISAM tables failed sometimes

when the data file was corrupt.

@item

Fixed a bug in @code{SHOW CREATE} when using auto_increment columns.

@item

Changed BDB tables to use new compare function in Berkeley DB 3.2.3

@item

You can now use Unix sockets with @code{mit-pthreads}

Added the latin5 (turkish) character set

@item

Small portability fixes

@end itemize

@node News-3.23.26, News-3.23.25, News-3.23.27, News-3.23.x

@appendixsubsec Changes in release 3.23.26

@itemize @bullet

@item

@item

Fixed bug in @code{FULLTEXT} index when inserting a @code{NULL} column.

@item

Changed to use @code{mkstemp()} instead of @code{tempnam()}.

Changed to use @code{mkstemp()} instead of @code{tempnam()}. Based

on a patch from John Jones.

@end itemize

@node News-3.23.25, News-3.23.24, News-3.23.26, News-3.23.x

@item

Fail safe replication.

@item

Optimize, test and document transactions safe tables

Optimize, test and document transactions safe tables (BDB tables)

@item

Allow users to change startup options.

@item

Fix configure so that one can compile all libraries (like @code{MyISAM})

without threads.

@item

Change to use mkstemp() instead of tempnam() for system that supports the call.

We need to add a my_mkstemp() function in mysys and also change the cache

code to not create the filename until we do the actual open.

Add an option to periodically flush key pages for tables with delayed keys

if they haven't been used in a while.

@item

Allow join on key parts (optimization issue).

@item