./databases/mysql55-server, MySQL 5, a free SQL database (server)

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]

Branch: CURRENT, Version: 5.5.40, Package name: mysql-server-5.5.40, Maintainer: pkgsrc-users

MySQL is a SQL (Structured Query Language) database server. SQL is the most
popular database language in the world. MySQL is a client-server implementation
that consists of a server daemon `mysqld' and many different client

The main goals of MySQL are speed and robustness.

The base upon which MySQL is built is a set of routines that have been used in
a highly demanding production environment for many years. While MySQL is still
in development it already offers a rich and highly useful function set.

The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL).

This package contains the MySQL server programs and libraries including
embedded server (by PKG_OPTION).

MESSAGE.sphinx [+/-]

Required to run:
[lang/perl5] [databases/mysql55-client]

Package options: embedded-server, ssl

Master sites: (Expand)

SHA1: b93a1b14ab2de390014e99b4293e7835da133196
RMD160: a0b6b9a390ba8a3abc889155d756656b28b98f70
Filesize: 21218.43 KB

Version history: (Expand)

CVS history: (Expand)

   2014-10-17 19:07:45 by Filip Hajny | Files touched by this commit (8)
Log message:
Add optional Sphinx SE plugin support to MySQL 5.5 and 5.6.
Intented as a clean implementation (replacement) of wip/mysql-sphinxse.

SphinxSE is MySQL storage engine which can be compiled into MySQL server 5.x
using its pluggable architecture. Despite the name, SphinxSE does not
actually store any data itself. It is actually a built-in client which
allows MySQL server to talk to searchd, run search queries, and obtain
search results. All indexing and searching happen outside MySQL.

See http://sphinxsearch.com/docs/current.ht … e-overview
   2014-10-09 15:45:06 by Thomas Klausner | Files touched by this commit (456)
Log message:
Remove SVR4_PKGNAME, per discussion on tech-pkg.
   2014-10-01 11:17:19 by Adam Ciarcinski | Files touched by this commit (4)
Log message:
Changes 5.5.40:
InnoDB: An ALTER TABLE ... ADD FOREIGN KEY operation could cause a serious error.
InnoDB: With a transaction isolation level less than or equal to READ COMMITTED, \ 
gap locks were not taken when scanning a unique secondary index to check for \ 
duplicates. As a result, duplicate check logic failed allowing duplicate key \ 
values in the unique secondary index.
InnoDB: During recovery, a segmentation fault would occur when marking a table \ 
as corrupt.
yaSSL client code did not validate the encryption size or session ID length, \ 
which could cause the client to exit.
MySQL installation from RPM packages could fail if Postfix had been installed \ 
using yum.
yaSSL could fail preauthorization if the client supplied inaccurate buffer lengths.
Competition between threads could lead to timeout failure trying to rotate the \ 
audit log file.
On Linux (OEL6), if Sun DTrace was installed, the MySQL build failed.
LPAD() and RPAD() could cause a server exit if the pad string argument was not \ 
well formed.
The optimizer could create a zero-length column for a temporary table, causing a \ 
server exit.
   2014-08-10 16:27:40 by Adam Ciarcinski | Files touched by this commit (4) | Package updated
Log message:
Changes 5.5.39:

CMake support was updated to handle CMake version 3.

The timed_mutexes system variable has no effect and is deprecated.

Bugs Fixed

InnoDB: Opening a parent table that has thousands of child tables could result \ 
in a long semaphore wait condition.

Partitioning: Selecting from a table having multiple columns in its primary key \ 
and partitioned by LIST COLUMNS(R), where R was the last (rightmost) column \ 
listed in the primary key definition, returned an incorrect result.

Replication: When using row-based replication, updating or deleting a row on the \ 
master that did not exist on the slave led to failure of the slave when it tried \ 
to process the change. This problem occurred with InnoDB tables lacking a \ 
primary key.

Replication: Quotation marks were not always handled correctly by LOAD DATA \ 
INFILE when written into the binary log.

Replication: A group of threads involved in acquiring locks could deadlock when \ 
the following events occurred:

Dump thread reconnects from slave; on master, a new dump thread tries to kill \ 
zombie dump threads; having acquired the thread's LOCK_thd_data, it is about to \ 
acquire LOCK_log.

Application thread executing show binary logs, having acquired LOCK_log and \ 
about to acquire LOCK_index.

Application thread executing PURGE BINARY LOGS; having acquired LOCK_index, it \ 
is about to acquire LOCK_thread_count.

Application thread executing SHOW PROCESSLIST (or SELECT * FROM \ 
INFORMATION_SCHEMA.PROCESSLIST), having acquired LOCK_thread_count and about to \ 
acquire the zombie dump thread's LOCK_thd_data.
   2014-07-16 10:56:59 by Filip Hajny | Files touched by this commit (2)
Log message:
The postinstall-solaris script is still being installed on SunOS.
   2014-06-14 12:21:52 by Sebastian Wiedenroth | Files touched by this commit (1)
Log message:
fix SMF Manifest installation by not overwriting INSTALLATION_DIRS
   2014-06-02 09:17:31 by Adam Ciarcinski | Files touched by this commit (4)
Log message:
Changes 5.5.38:

Bugs Fixed

InnoDB: For each insert, memset would be called three times to allocate memory \ 
for system fields. To reduce CPU usage, the three memset calls are now combined \ 
into a single call.

Replication: When used on a table employing a transactional storage engine, a \ 
failed TRUNCATE TABLE was still written to the binary log and thus replayed on \ 
the slave. This could lead to inconsistency when the master retained data that \ 
was removed on the slave.

Now in such cases TRUNCATE TABLE is logged only when it executes successfully.

Certain INFORMATION_SCHEMA queries could cause a server exit.

For indexes on prefixes or character string columns, index corruption could \ 
occur for assignment of binary data to the column due to improper character \ 

Solaris-specific scripts were included in and installed by non-Solaris packages.

EXPLAIN on a query with an EXISTS subquery containing a UNION could cause a \ 
server exit. Multiple executions of a prepared EXPLAIN on a UNION of subqueries \ 
could cause a server exit.

Executing a correlated subquery on an ARCHIVE table which has an AUTO_INCREMENT \ 
column caused the server to hang.

The client library could cause clients to exit due to incorrectly mapping the \ 
client error number to the corresponding message, if reallocation of packet \ 
buffer memory occurred.

Calling mysql_get_server_version() with an invalid connection handler argument \ 
caused the client to exit. Now it returns 0 and reports a \ 

On Windows, calling mysql_thread_init() call without mysql_init() caused the \ 
client to exit. windows. Now it returns a nonzero result because it is an error \ 
to call mysql_thread_init() before the client library is initialized with \ 

CMake produced not-useful warnings about INTERFACE_LINK_LIBRARIES policy.

LOAD DATA LOCAL INFILE could use all CPU if import errors occurred when there \ 
were no line delimiters.

A statement of the following form broke row-based replication because it created \ 
a table having a field of data type BIGINT with a display width of 3000, which \ 
is beyond the maximum acceptable value of 255:

   2014-04-14 02:02:50 by Blue Rats | Files touched by this commit (9)
Log message:
Don't hardcode PID file. Instead, give the user the option to set it. The
rc.d script overrides my.cnf directives. Hardcoding the PID can cause a
problem on systems transitioning to MySQL packages from pkgsrc.