Johan Wikman 62b0e5fab0 Session info always copied to tls
Maxadmin earlier gave the impression that you could change whether
messages for different log files could be specifically enabled for
a session. In practice that was true only for trace messages as the
session id and the bitmask telling what logfiles are enabled, were
copied to thread local storage only as far as trace messages were
concered.

The code for setting that information in place is quit short and
efficient, so there is really no reason not to do that always.
This also means that it always will be possible to get your hands
on the session object if there is a need for that.
2015-11-23 18:14:46 +02:00
2015-11-23 13:06:39 +02:00
2015-04-26 20:08:27 +03:00
2015-11-23 18:14:46 +02:00
2014-10-15 14:59:24 +01:00
2015-11-19 17:17:16 +02:00
2013-12-16 17:20:50 +00:00
2015-04-14 20:36:29 +03:00
2015-07-15 17:21:24 +03:00
2015-03-23 12:05:02 +02:00

MaxScale by MariaDB Corporation

The MariaDB Corporation MaxScale is an intelligent proxy that allows forwarding of database statements to one or more database servers using complex rules, a semantic understanding of the database statements and the roles of the various servers within the backend cluster of databases.

MaxScale is designed to provide load balancing and high availability functionality transparently to the applications. In addition it provides a highly scalable and flexible architecture, with plugin components to support different protocols and routing decisions.

MaxScale is implemented in C and makes extensive use of the asynchronous I/O capabilities of the Linux operating system. The epoll system is used to provide the event driven framework for the input and output via sockets.

The protocols are implemented as external shared object modules which can be loaded at runtime. These modules support a fixed interface, communicating the entries points via a structure consisting of a set of function pointers. This structure is called the "module object".

The code that routes the queries to the database servers is also loaded as external shared objects and are referred to as routing modules.

An Google Group exists for MaxScale that can be used to discuss ideas, issues and communicate with the MaxScale community. Send email to maxscale@googlegroups.com or use the forum interface

Bugs can be reported in the MariaDB Corporation bugs database https://mariadb.atlassian.net/projects/MXS/issues

Documentation

For information about installing and using MaxScale, please refer to the documentation.

Description
No description provided
Readme 118 MiB
Languages
C 50.9%
C++ 30.8%
Shell 3.7%
HTML 3.2%
Tcl 3.1%
Other 8.1%