summaryrefslogtreecommitdiff
path: root/finance
diff options
context:
space:
mode:
authorxtraeme <xtraeme@pkgsrc.org>2005-01-17 14:42:35 +0000
committerxtraeme <xtraeme@pkgsrc.org>2005-01-17 14:42:35 +0000
commit71125409caf0f3db796816a8c860d02dd510cfc4 (patch)
tree0da4a97133219ba9bc053832cff8452e4ead9e32 /finance
parentccce7873debd8e4a12f2c1163fc532a92fb00f12 (diff)
downloadpkgsrc-71125409caf0f3db796816a8c860d02dd510cfc4.tar.gz
Update mysql4-{client,server} to 4.1.9.
Functionality added or changed: * The Mac OS X 10.3 installation disk images now include a MySQL Preference Pane for the Mac OS X Control Panel that enables the user to start and stop the MySQL server via the GUI and activate and deactivate the automatic MySQL server startup on bootup. * Seconds_Behind_Master will be NULL (which means ``unknown'') if the slave SQL thread is not running, or if the slave I/O thread is not running or not connected to master. It will be zero if the SQL thread has caught up with the I/O thread. It no longer grows indefinitely if the master is idle. * InnoDB: Do not acquire an internal InnoDB table lock in LOCK TABLES if AUTOCOMMIT=1. This helps in porting old MyISAM applications to InnoDB. InnoDB table locks in that case caused deadlocks very easily. * InnoDB: Print a more descriptive error and refuse to start InnoDB if the size of `ibdata' files is smaller than what is stored in the tablespace header; innodb_force_recovery overrides this. * The MySQL server aborts immediately instead of simply issuing a warning if it is started with the --log-bin option but cannot initialize the binary log at startup (that is, an error occurs when writing to the binary log file or binary log index file). * The binary log file and binary log index file now behave like MyISAM when there is a "disk full" or "quota exceeded" error. See section A.4.3 How MySQL Handles a Full Disk. Many bugfixes were fixed... see http://dev.mysql.com/doc/mysql/en/News-4.1.9.html
Diffstat (limited to 'finance')
0 files changed, 0 insertions, 0 deletions