Johan Wikman 90fdbf8860 MXS-1652 Add possibility to log SQL statements
With the flag --debug=enable-statement-logging it is now possible
to instruct MaxScale to log all SQL statements it sends to the
servers.

The format of the logged string looks like:

    notice : SQL(127.0.0.1): 0, "SELECT ..."

First the fixed string "SQL", followed by the server address in
parenthesis followed by the actual return value of mysql_query(),
followed by the statement itself.

The "SQL" string makes the lines easy to grep for and having the
return value before the statement makes it easier to spot since
the length of the return value string does not wary much, but the
length of the statements do wary a lot.
2018-02-06 14:30:29 +02:00
2017-07-03 17:08:39 +03:00
2018-01-30 16:28:11 +02:00
2017-09-20 10:47:53 +03:00
2018-01-30 11:08:41 +02:00
2017-09-12 11:17:19 +03:00
2018-02-02 16:05:14 +02:00
2017-09-21 09:36:50 +03:00
2017-11-27 09:10:33 +02:00
2017-06-01 10:24:20 +03:00
2018-01-22 15:29:21 +02:00
2018-01-16 09:47:49 +02:00
2017-05-29 21:50:29 +03:00
2017-06-01 19:39:41 +03:00
2017-06-01 10:42:21 +03:00
2017-04-20 16:03:41 +03:00
2017-06-20 10:45:02 +03:00
2018-01-08 14:28:13 +02:00
2018-01-29 15:33:29 +02:00

MaxScale by MariaDB Corporation

Build Status

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.

We're also on the #maria and #maxscale channels on FreeNode.

Please report all feature requests, improvements and bugs in the MariaDB Jira.

Documentation

For information about installing and using MaxScale, please refer to the documentation. The official documentation can be found on the MariaDB Knowledge Base.

The module and configuration documentation can be found in the Documentation directory of the source tree.

Contributing Code

Read the Contributing page on the wiki for more information on how to do pull request and where to do them.

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%