diff --git a/Documentation/Release-Notes/MaxScale-0.5-Release-Notes.md b/Documentation/Release-Notes/MaxScale-0.5-Release-Notes.md
deleted file mode 100644
index 5f09d7bfd..000000000
--- a/Documentation/Release-Notes/MaxScale-0.5-Release-Notes.md
+++ /dev/null
@@ -1,336 +0,0 @@
-# MariaDB MaxScale 0.5 Alpha Release Notes
-
-0.5 Alpha
-
-This document details the changes in version 0.5 since the release of the 0.4 alpha of the MaxScale product.
-
-# New Features
-
-## Read/Write Splitter Routing Module
-
-In previous versions the read/write splitter routing module has had a number of limitations on it use, in the alpha release the router now removes the most important restrictions.
-
-### Session Commands
-
-Session commands are those statements that make some change to the user’s login session that may cause different effects from subsequent statements executed. Since the read/write splitter executes statements on either a master server or a slave server, depending upon the statement to execute, it is important that these session modifications are executed on all connections to both slave and master servers. This is resolved in release 0.5 such that session modification commands are executed on all active connections and a single return is forward back to the client that made the request.
-
-### Transaction Support
-
-Transaction support has been added into this version of the read/write splitter, there is one known outstanding limitation. If autocommit is enabled inside an active transaction it is not considered as commit in read/write splitter. Once a transaction has started all statements are routed to a master until the transaction is committed or rolled back.
-
-## Authentication
-
-A number of issues and shortcomings in the authentication performed by MaxScale have been resolved by this release.
-
-### Host Considered in Authentication
-
-Previously MaxScale did not follow the same rules as MySQL when authenticating a login request, it would always use the wildcard password entries and would not check the incoming host was allowed to connect. MaxScale now checks the incoming IP address for a connection request and verifies this against the authentication data loaded from the backend servers. The same rules are applied when choosing the password entry to authenticate with. Note however that authentication from MaxScale to the backend database will fail if the MaxScale host is not allowed to login using the matching password for the user.
-
-### Stale Authentication Data
-
-In previous releases of MaxScale the authentication data would be read at startup time only and would not be refreshed. Therefore if a user was added or modified in the backend server this will not be picked up by MaxScale and that user would be unable to connect via MaxScale. MaxScale now reloads user authentication data when a failure occurs and will refresh its internal tables if the data has changed in the backend. Please note that this reload process is rate limited to prevent incorrect logins to MaxScale being used for a denial of service attack on the backend servers.
-
-### Enable Use Of "root" User
-
-Previously MaxScale would prevent the use of the root user to login to the backend servers via MaxScale. This may be enabled on a per service basis by adding an "enable_root_user" options in the service entry to enable it in the MaxScale configuration file. This allows the use of root to be controlled on a per service basis.
-
-## Network Support
-
-### Unix Domain Sockets
-
-MaxScale now supports Unix domain sockets for connecting to a local MaxScale server. The use of a Unix domain socket is controlled by adding a "socket" entry in the listener configuration entry for a service.
-
-### Network Interface Binding
-
-MaxScale has added the ability to bind a listener for a service to a network address via an "address" entry in the configuration file.
-
-# Server Version
-
-The server version reported when connected to a database via MaxScale has now been altered. This now shows the MaxScale name and version together with the backend server name. An example of this can be seen below for the 0.5 release.
-
--bash-4.1$ mysql -h 127.0.0.1 -P 4006 -uxxxx -pxxxx
Welcome to the MariaDB monitor. Commands end with ; or \\g.
Your MySQL connection id is 22320
Server version: MaxScale 0.5.0 MariaDB Server
Copyright (c) 2000, 2012, Oracle, Monty Program Ab and others.
Type 'help;' or '\\h' for help. Type '\\c' to clear the current input statement.
MySQL [(none)]> \\ys
--------------
mysql Ver 15.1 Distrib 5.5.28a-MariaDB, for Linux (i686) using readline 5.1
...
Server: MySQL
Server version: MaxScale 0.5.0 MariaDB Server
...
--------------
MySQL [(none)]>
-
-# Bug Fixes
-
-A number of bug fixes have been applied between the 0.4 alpha and this alpha release. The table below lists the bugs that have been resolved. The details for each of these may be found in bugs.skysql.com.
-
-
-
- ID |
- Summary |
-
-
- 141 |
- No "delete user" command in debugcli |
-
-
- 175 |
- Buffer leak in dcb_read from Coverity run |
-
-
- 178 |
- Uninitialised variables from Coverity run |
-
-
- 179 |
- open with O_CREAT in second argument needs 3 arguments |
-
-
- 363 |
- simple_mutex "name" memory handling ... |
-
-
- 126 |
- "reload config" in debug interface causes maxscale server to segfault |
-
-
- 149 |
- It is possible to delete all maxscale users |
-
-
- 218 |
- there is no way to understand what is going on if MAXSCALE_HOME is incorrect |
-
-
- 137 |
- "show users" and "reload users" refer to very different things in debugcli |
-
-
- 154 |
- readwritesplit does not use router_options |
-
-
- 160 |
- telnetd leaks memory |
-
-
- 169 |
- Galera monitor is actually never compiled .... |
-
-
- 172 |
- Several compile errors in galera_mon.c |
-
-
- 174 |
- Resource leak in server.c |
-
-
- 176 |
- Resource leak in gw_utils.c |
-
-
- 362 |
- possible datadir_cleanup() problems ... |
-
-
- 124 |
- readconnroute does not validate router_options |
-
-
- 153 |
- MaxScale fails when max connections are exceeded |
-
-
- 133 |
- MaxScale leaves lots of "data" directories sitting around $MAXSCALE_HOME |
-
-
- 166 |
- readwritesplit causes MaxScale segfault when starting up |
-
-
- 207 |
- Quitting telnet session causes maxscale to fail |
-
-
- 161 |
- Memory leak in load_mysql_users. |
-
-
- 177 |
- Resource leak in secrets.c |
-
-
- 182 |
- On Startup logfiles are empty |
-
-
- 135 |
- MaxScale unsafely handles empty passwords in getUsers |
-
-
- 145 |
- .secret file for encrypted passwords cyclicly searched |
-
-
- 171 |
- ifndef logic in build_gateway.inc doesn't work, MARIADB_SRC_PATH from env not picked up |
-
-
- 173 |
- Resource leak in adminusers.c found by Coverity |
-
-
- 376 |
- Confusing Server Version |
-
-
- 370 |
- maxscale binary returns zero exit status on failures |
-
-
- 150 |
- telnetd listener should bind to 127.0.0.1 by default |
-
-
- 152 |
- listener configuration should support bind address |
-
-
- 373 |
- Documentation: it's not clear what privileges the maxscale user needs |
-
-
- 128 |
- Maxscale prints debug information to terminal session when run in background |
-
-
- 129 |
- MaxScale refuses to connect to server and reports nonsense error as a result |
-
-
- 147 |
- Maxscale's hashtable fails to handle deletion of entries. |
-
-
- 148 |
- users data structure's stats have incorrect values. |
-
-
- 384 |
- MaxScale crashes if backend authentication fails |
-
-
- 210 |
- Bad timing in freeing readconnrouter's dcbs cause maxscale crash |
-
-
- 403 |
- gwbuf_free doesn't protect freeing shared buffer |
-
-
- 371 |
- If router module load fails, MaxScale goes to inifinite loop |
-
-
- 385 |
- MaxScale (DEBUG-version) dasserts if backend dcb is closed in the middle of client dcb performing close_dcb |
-
-
- 386 |
- Starting MaxScale with -c pointing at existing file causes erroneous behavior |
-
-
- 209 |
- Error in backend hangs client connection |
-
-
- 194 |
- maxscale crashes at start if module load fails |
-
-
- 369 |
- typo in "QUERY_TYPE_UNKNWON" |
-
-
- 163 |
- MaxScale crashes with multiple threads |
-
-
- 162 |
- threads parameter in configuration file is not effective |
-
-
- 400 |
- hastable_get_stats returns value of uninitialized value in 'nelems' |
-
-
- 212 |
- Failing write causes maxscale to fail |
-
-
- 222 |
- Double freeing mutex corrupts log |
-
-
- 208 |
- current_connection_count is decreased multiple times per session, thus breaking load balancing logic |
-
-
- 378 |
- Misspelling maxscale section name in config file crashes maxscale |
-
-
- 399 |
- Every row in log starts with 0x0A00 |
-
-
- 205 |
- MaxScale crashes due SEGFAULT because return value of dcb_read is not checked |
-
-
- 220 |
- Maxscale crash if socket listening fails in startup |
-
-
- 372 |
- Log manager hangs MaxScale if log string (mostly query length) exceeds block size |
-
-
- 397 |
- Free of uninitialised pointer if MAXSCALE_HOME is not set |
-
-
- 402 |
- gw_decode_mysql_server_handshake asserts with mysql 5.1 backend |
-
-
- 345 |
- MaxScale don't find backend servers if they are started after MaxScale |
-
-
- 406 |
- Memory leak in dcb_alloc() |
-
-
- 360 |
- MaxScale passwd option |
-
-
- 151 |
- Get parse_sql failed on array INSERT |
-
-
- 216 |
- Backend error handling doesn't update server's connection counter |
-
-
- 127 |
- MaxScale should handle out-of-date backend auth data more gracefully |
-
-
- 146 |
- "show dbusers" argument not documented |
-
-
- 125 |
- readconnroute causes maxscale server crash if no slaves are available |
-
-
- 375 |
- Tarball contains UID and maxscale base dir |
-
-
-
-
diff --git a/Documentation/Release-Notes/MaxScale-0.6-Release-Notes.md b/Documentation/Release-Notes/MaxScale-0.6-Release-Notes.md
deleted file mode 100644
index 4b2c445c3..000000000
--- a/Documentation/Release-Notes/MaxScale-0.6-Release-Notes.md
+++ /dev/null
@@ -1,31 +0,0 @@
-# MariaDB MaxScale 0.6 Alpha Release Notes
-
-0.6 Alpha
-
-This document details the changes in version 0.6 since the release of the 0.5 alpha of the MaxScale product. The 0.6 version is merely a set of bug fixes based on the previous 0.5 version.
-
-# Bug Fixes
-
-A number of bug fixes have been applied between the 0.5 alpha and this alpha release. The table below lists the bugs that have been resolved. The details for each of these may be found in bugs.skysql.com.
-
-
-
- ID |
- Summary |
-
-
- 462 |
- Testall target fails in server/test to invalid MAXSCALE_HOME path specification |
-
-
- 467 |
- max_slave_replication lag is not effective after session creation |
-
-
- 468 |
- query_classifier : if parsing fails, parse tree and thread context are freed but used |
-
-
- 469 |
- rwsplit counts every connection twice in master - connection counts leak |
-
-
- 466 |
- hint_next_token doesn't detect = pair if there are no spaces around '=' |
-
-
- 470 |
- Maxscale crashes after a normal query if a query with named hint was used before |
-
-
- 473 |
- Entering a hint with route server target as '=(' causes a crash |
-
-
- 472 |
- Using a named hint after its initial use causes a crash |
-
-
- 471 |
- Routing Hints route to server sometimes doesn't work |
-
-
- 463 |
- MaxScale hangs receiving more than 16K in input |
-
-
- 476 |
- mysql_common.c:protocol_archive_srv_command leaks memory and accesses freed memory |
-
-
- 479 |
- Undefined filter reference in maxscale.cnf causes a crash |
-
-
- 410 |
- maxscale.cnf server option is not parsed for spaces |
-
-
- 417 |
- Galera monitor freezes on network failure of a server |
-
-
- 488 |
- SHOW VARIABLES randomly failing with "Lost connection to MySQL server" |
-
-
- 484 |
- Hashtable does not always release write lock during add |
-
-
- 485 |
- Hashtable not locked soon enough in iterator get next item |
-
-
- 493 |
- Can have same section name multiple times without warning |
-
-
- 510 |
- Embedded library crashes on a call to free_embedded_thd |
-
-
- 511 |
- Format strings in log_manager.cc should be const char* |
-
-
- 509 |
- rw-split sensitive to order of terms in field list of SELECT |
-
-
- 507 |
- rw-split router does not send last_insert_id() to master |
-
-
- 490 |
- session handling for non-determinstic user variables broken |
-
-
- 489 |
- @@hostname and @@server_id treated differently from @@wsrep_node_address |
-
-
- 528 |
- Wrong service name in tee filter crashes maxscale on connect |
-
-
- 530 |
- MaxScale socket permission |
-
-
- 536 |
- log_manager doesn't write buffers to disk in the order they are written |
-
-
- 447 |
- Error log is flooded with same warning if there are no slaves present |
-
-
- 475 |
- The end comment tag in hints isn't properly detected. |
-
-
- 181 |
- Missing log entry if server not reachable |
-
-
- 486 |
- Hashtable problems when created with size less than one |
-
-
- 516 |
- maxadmin CLI client sessions are not closed? |
-
-
- 495 |
- Referring to a nonexisting server in servers=... doesn't even raise a warning |
-
-
- 538 |
- maxscale should expose details of "Down" server |
-
-
- 539 |
- MaxScale crashes in session_setup_filters |
-
-
- 494 |
- The service 'CLI' is missing a definition of the servers that provide the service |
-
-
- 180 |
- Documentation: No information found in the documentation about firewall settings |
-
-
- 524 |
- Connecting to MaxScale from localhost tries matching @127.0.0.1 grant |
-
-
- 481 |
- MySQL monitor doesn't set master server if the replication is broken |
-
-
- 437 |
- Failure to detect MHA master switch |
-
-
- 541 |
- Long queries cause MaxScale to block |
-
-
- 492 |
- In dcb.c switch fallthrough appears to be used without comment |
-
-
- 439 |
- Memory leak in getUsers |
-
-
- 545 |
- RWSplit: session modification commands weren't routed to all if executed inside open transaction |
-
-
- 543 |
- RWSplit router statistics counters are not updated correctly |
-
-
- 544 |
- server with weight=0 gets one connection |
-
-
- 525 |
- Crash when saving post in Wordpress |
-
-
- 533 |
- Drupal installer hangs |
-
-
- 497 |
- Can’t enable debug/trace logs in configuration file |
-
-
- 430 |
- Temporary tables not working in MaxScale |
-
-
- 527 |
- No signal handler for segfault etc |
-
-
- 546 |
- Use of weightby router parameter causes error log write |
-
-
- 506 |
- Don’t write shm/tmpfs by default without telling the user or giving a way to override it |
-
-
- 552 |
- Long argument options to maxadmin and maxscale broke maxadmin commands |
-
-
- 521 |
- Many commands in maxadmin client simply hang |
-
-
- 478 |
- Parallel session command processing fails |
-
-
- 499 |
- make clean leavessoem .o files behind |
-
-
- 500 |
- "depend: no such file warnings during make |
-
-
- 501 |
- log_manager, query classifier rebuilds unconditionally |
-
-
- 502 |
- log_manager and query_classifier builds always rebuild utils |
-
-
- 504 |
- clean rule for Documentation directory in wrong makefile |
-
-
- 505 |
- utils/makefile builds stuff unconditionally, misses "depend" target |
-
-
- 548 |
- MaxScale accesses freed client DCB and crashes |
-
-
- 550 |
- modutil functions process length incorrectly |
-
-
-
-
-# Packaging
-
-Both RPM and Debian packages are available for MaxScale in addition to the tar based releases previously distributed we now provide
-
-* CentOS/RedHat 5 RPM
-
-* CentOS/RedHat 6 RPM
-
-* Ubuntu 14.04 package
-
diff --git a/Documentation/Release-Notes/MaxScale-1.0.3-Release-Notes.md b/Documentation/Release-Notes/MaxScale-1.0.3-Release-Notes.md
deleted file mode 100644
index db8329366..000000000
--- a/Documentation/Release-Notes/MaxScale-1.0.3-Release-Notes.md
+++ /dev/null
@@ -1,136 +0,0 @@
-# MariaDB MaxScale 1.0.3 Release Notes
-
-1.0.3 GA
-
-This document details the changes in version 1.0.3 since the release of the 1.0.2 Release Candidate of the MaxScale product.
-
-# New Features
-
-No new features have been introduced since the released candidate was released.
-
-# Bug Fixes
-
-A number of bug fixes have been applied between the 0.6 alpha and this alpha release. The table below lists the bugs that have been resolved. The details for each of these may be found in bugs.mariadb.com.
-
-
-
- ID |
- Summary |
-
-
- 644 |
- Buffered that were cloned using the gwbuf_clone routine failed to initialise the buffer lock structure correctly. |
-
-
- 643 |
- Recursive filter definitions in the configuration file could cause MaxScale to loop |
-
-
- 665 |
- An access to memory that had already been freed could be made within the MaxScale core |
-
-
- 664 |
- MySQL Authentication code could access memory that had already been freed. |
-
-
- 673 |
- MaxScale could crash if it had an empty user table and the MaxAdmin show dbusers command was run |
-
-
- 670 |
- The tee filter could lose statement on the branch service if the branch service was significantly slower at executing statements compared with the main service. |
-
-
- 653 |
- Memory corruption could occur with extremely long hostnames in the mysql.user table. |
-
-
- 657 |
- If the branch service of a tee filter shutdown unexpectedly then MaxScale could fail |
-
-
- 654 |
- Missing quotes in MaxAdmin show dbusers command could cause MaxAdmin to crash |
-
-
- 677 |
- A race condition existed in the tee filter client reply handling |
-
-
- 658 |
- The readconnroute router did not correctly close sessions when a backend database failed |
-
-
- 662 |
- MaxScale startup hangs if no backend servers respond |
-
-
- 676 |
- MaxScale writes a log entry, "Write to backend failed. Session closed." when changing default database via readwritesplit with max_slave_connections != 100% |
-
-
- 650 |
- Tee filter does not correctly detect missing branch service |
-
-
- 645 |
- Tee filter can hang MaxScale if the read/write splitter is used |
-
-
- 678 |
- Tee filter does not always send full query to branch service |
-
-
- 679 |
- A shared pointer in the service was leading to misleading service states |
-
-
- 680 |
- The Read/Write Splitter can not load users if there are no databases available at startup |
-
-
- 681 |
- The Read/Write Splitter could crash is the value of max_slave_connections was set to a low percentage and only a small number of backend servers are available |
-
-
-
-
-# Known Issues
-
-There are a number bugs and known limitations within this version of MaxScale, the most serious of this are listed below.
-
-* The SQL construct "LOAD DATA LOCAL INFILE" is not fully supported.
-
-* The Read/Write Splitter is a little too strict when it receives errors from slave servers during execution of session commands. This can result in sessions being terminated in situation in which MaxScale could recover without terminating the sessions.
-
-* MaxScale can not manage authentication that uses wildcard matching in hostnames in the mysql.user table of the backend database. The only wildcards that can be used are in IP address entries.
-
-* When users have different passwords based on the host from which they connect MaxScale is unable to determine which password it should use to connect to the backend database. This results in failed connections and unusable usernames in MaxScale.
-
-# Packaging
-
-Both RPM and Debian packages are available for MaxScale in addition to the tar based releases previously distributed we now provide
-
-* CentOS/RedHat 5
-
-* CentOS/RedHat 6
-
-* CentOS/RedHat 7
-
-* Debian 6
-
-* Debian 7
-
-* Ubuntu 12.04 LTS
-
-* Ubuntu 13.10
-
-* Ubuntu 14.04 LTS
-
-* Fedora 19
-
-* Fedora 20
-
-* OpenSuSE 13
-
diff --git a/Documentation/Release-Notes/MaxScale-1.0.4-Release-Notes.md b/Documentation/Release-Notes/MaxScale-1.0.4-Release-Notes.md
deleted file mode 100644
index 9103c830a..000000000
--- a/Documentation/Release-Notes/MaxScale-1.0.4-Release-Notes.md
+++ /dev/null
@@ -1,140 +0,0 @@
-# MariaDB MaxScale 1.0.4 Release Notes
-
-1.0.4 GA
-
-This document details the changes in version 1.0.4 since the release of the 1.0.2 Release Candidate of the MaxScale product.
-
-## New Features
-
-No new features have been introduced since the released candidate was released.
-
-## Bug Fixes
-
-A number of bug fixes have been applied between the 0.6 alpha and this alpha release. The table below lists the bugs that have been resolved. The details for each of these may be found in bugs.mariadb.com.
-
-
-
- ID |
- Summary |
-
-
- 644 |
- Buffered that were cloned using the gwbuf_clone routine failed to initialise the buffer lock structure correctly. |
-
-
- 643 |
- Recursive filter definitions in the configuration file could cause MaxScale to loop |
-
-
- 665 |
- An access to memory that had already been freed could be made within the MaxScale core |
-
-
- 664 |
- MySQL Authentication code could access memory that had already been freed. |
-
-
- 673 |
- MaxScale could crash if it had an empty user table and the MaxAdmin show dbusers command was run |
-
-
- 670 |
- The tee filter could lose statement on the branch service if the branch service was significantly slower at executing statements compared with the main service. |
-
-
- 653 |
- Memory corruption could occur with extremely long hostnames in the mysql.user table. |
-
-
- 657 |
- If the branch service of a tee filter shutdown unexpectedly then MaxScale could fail |
-
-
- 654 |
- Missing quotes in MaxAdmin show dbusers command could cause MaxAdmin to crash |
-
-
- 677 |
- A race condition existed in the tee filter client reply handling |
-
-
- 658 |
- The readconnroute router did not correctly close sessions when a backend database failed |
-
-
- 662 |
- MaxScale startup hangs if no backend servers respond |
-
-
- 676 |
- MaxScale writes a log entry, "Write to backend failed. Session closed." when changing default database via readwritesplit with max_slave_connections != 100% |
-
-
- 650 |
- Tee filter does not correctly detect missing branch service |
-
-
- 645 |
- Tee filter can hang MaxScale if the read/write splitter is used |
-
-
- 678 |
- Tee filter does not always send full query to branch service |
-
-
- 679 |
- A shared pointer in the service was leading to misleading service states |
-
-
- 680 |
- The Read/Write Splitter can not load users if there are no databases available at startup |
-
-
- 681 |
- The Read/Write Splitter could crash is the value of max_slave_connections was set to a low percentage and only a small number of backend servers are available |
-
-
-
-
-## Known Issues
-
-There are a number bugs and known limitations within this version of MaxScale, the most serious of this are listed below.
-
-* The SQL construct "LOAD DATA LOCAL INFILE" is not fully supported.
-
-* The Read/Write Splitter is a little too strict when it receives errors from slave servers during execution of session commands. This can result in sessions being terminated in situation in which MaxScale could recover without terminating the sessions.
-
-* MaxScale can not manage authentication that uses wildcard matching in hostnames in the mysql.user table of the backend database. The only wildcards that can be used are in IP address entries.
-
-* When users have different passwords based on the host from which they connect MaxScale is unable to determine which password it should use to connect to the backend database. This results in failed connections and unusable usernames in MaxScale.
-
-# Packaging
-
-Both RPM and Debian packages are available for MaxScale in addition to the tar based releases previously distributed we now provide
-
-* CentOS/RedHat 5
-
-* CentOS/RedHat 6
-
-* CentOS/RedHat 7
-
-* Debian 6
-
-* Debian 7
-
-* Ubuntu 12.04 LTS
-
-* Ubuntu 13.10
-
-* Ubuntu 14.04 LTS
-
-* Fedora 19
-
-* Fedora 20
-
-* OpenSuSE 13
-
-# MaxScale Home Default Value
-
-The installation assumes that the default value for the environment variable MAXSCALE_HOME is set to /usr/local/mariadb/maxscale. This is hard coded in the service startup file that is placed in /etc/init.d/maxscale by the installation process.
-
diff --git a/Documentation/Release-Notes/MaxScale-1.0.5-Release-Notes.md b/Documentation/Release-Notes/MaxScale-1.0.5-Release-Notes.md
deleted file mode 100644
index e979ff6c1..000000000
--- a/Documentation/Release-Notes/MaxScale-1.0.5-Release-Notes.md
+++ /dev/null
@@ -1,113 +0,0 @@
-# MariaDB MaxScale 1.0.5 Release Notes
-
-This document details the changes in version 1.0.5 since the release of the 1.0.4 GA of the MaxScale product.
-
-# New Features
-No new features have been introduced since the GA version was released. SuSE Enterprise 11 and 12 packages are now also supplied.
-
-# Bug Fixes
-
-A number of bug fixes have been applied between the 1.0.4 initial GA release and this GA release. The table below lists the bugs that have been resolved. The details for each of these may be found in bugs.mariadb.com.
-
-
-
- ID |
- Summary |
-
-
- 519 |
- LOAD DATA LOCAL INFILE not handled? |
-
-
- 714 |
- Error log flooded when too many connect errors causes the MaxScale host to be blocked |
-
-
- 711 |
- Some MySQL Workbench Management actions hang with R/W split router |
-
-
- 710 |
- make package install files in /etc/init.d |
-
-
- 683 |
- Check for unsupported version of MariaDB |
-
-
- 684 |
- Use mysql_config to determine include/lib directory paths and compiler options |
-
-
- 689 |
- cmake DCMAKE_INSTALL_PREFIX has no effect |
-
-
- 701 |
- set server maint fails on the command line |
-
-
- 705 |
- Authentication fails when the user connects to a database with the SQL mode including ANSI_QUOTES |
-
-
- 507 |
- R/W split does not send last_insert_id() to the master |
-
-
- 700 |
- maxscale version has no output |
-
-
- 694 |
- RWSplit SELECT @a:=@a+1 as a, test.b from test breaks client session |
-
-
- 685 |
- SELECT against readconnrouter fails when large volumes of data are returned and the tee filter is used |
-
-
-
-# Known Issues
-
-There are a number bugs and known limitations within this version of MaxScale, the most serious of this are listed below.
-
-* The Read/Write Splitter is a little too strict when it receives errors from slave servers during execution of session commands. This can result in sessions being terminated in situation in which MaxScale could recover without terminating the sessions.
-
-* MaxScale can not manage authentication that uses wildcard matching in hostnames in the mysql.user table of the backend database. The only wildcards that can be used are in IP address entries.
-
-* When users have different passwords based on the host from which they connect MaxScale is unable to determine which password it should use to connect to the backend database. This results in failed connections and unusable usernames in MaxScale.
-
-# Packaging
-
-Both RPM and Debian packages are available for MaxScale in addition to the tar based releases previously distributed we now provide
-
-* CentOS/RedHat 5
-
-* CentOS/RedHat 6
-
-* CentOS/RedHat 7
-
-* Debian 6
-
-* Debian 7
-
-* Ubuntu 12.04 LTS
-
-* Ubuntu 13.10
-
-* Ubuntu 14.04 LTS
-
-* Fedora 19
-
-* Fedora 20
-
-* OpenSuSE 13
-
-* SuSE Enterprise 11
-
-* SuSE Enterprise 12
-
-# MaxScale Home Default Value
-
-The installation assumes that the default value for the environment variable MAXSCALE_HOME is set to /usr/local/skysql/maxscale. This is hard coded in the service startup file that is placed in /etc/init.d/maxscale by the installation process.
diff --git a/Documentation/Release-Notes/MaxScale-1.1-Release-Notes.md b/Documentation/Release-Notes/MaxScale-1.1-Release-Notes.md
deleted file mode 100644
index e2d0f505c..000000000
--- a/Documentation/Release-Notes/MaxScale-1.1-Release-Notes.md
+++ /dev/null
@@ -1,284 +0,0 @@
-# MariaDB MaxScale 1.1 Release Notes
-
-## 1.1 GA
-
-This document details the changes in version 1.1 since the release of the 1.0.5 GA Release of the MaxScale product.
-
-## New Features
-
-### High Performance Binlog Relay
-Replicate Binlog from the master to slave through MaxScale as simplified relay server for reduced network load and disaster recovery
-
-### Database Firewall Filter
-Block queries based on columns in the query, where condition, query type(select, insert, delete, update), presence of wildcard in column selection, regular expression match and time of the query
-
-### Schema Sharding Router
-Route to databases sharded by schema without application level knowledge of shard configuration
-
-### Hint based routing
-Pass hints in the SQL statement to influence the routing decision based on replication lag or time out
-
-### Named Server Routing
-Routing to a named server if incoming query matches a regular expression
-
-### Canonical Query logging
-Convert incoming queries to canonical form and push the query and response into RabbitMQ Broker for a RabbitMQ Client to later retrieve from
-
-### Nagios Plugin
-Plugin scripts for monitoring MaxScale status and performance from a Nagios Server
-
-### Notification Service
-Receive notification of security update and patches tailored to your MaxScale configuration
-
-### MySQL NDB cluster support
-Connection based routing to MySQL NDB clusters
-
-### Updated installation path
-MaxScale is now installed into `/usr/local/mariadb-maxscale`
-
-## Bug Fixes
-
-A number of bug fixes have been applied between the 1.0.5 GA and this GA release. The table below lists the bugs that have been resolved. The details for each of these may be found in https://jira.mariadb.org/projects/MXS or in the former http://bugs.mariadb.com Bug database
-
-
-
- ID |
- Summary |
-
-
- MXS-80 |
- "show sessions" can crash MaxScale |
-
-
- MXS-79 |
- schemarouter hangs if client connects with empty database |
-
-
- MXS-78 |
- "USE" statement gives unpredictable/unexpected results |
-
-
- MXS-76 |
- core/dbusers.c needs better error messages |
-
-
- MXS-74 |
- Crash when no arguments given to on_queries clause |
-
-
- MXS-72 |
- dbfwfilter on_queries clause appears to be ignored |
-
-
- MXS-71 |
- dbfwfilter at_times clause seems to erroneously block user |
-
-
- MXS-68 |
- Wrong rule name in dbfwfilter leads to MaxScale crash |
-
-
- MXS-65 |
- Omitting in users directive causes crash in libdbfwfilter.so(link_rules) |
-
-
- MXS-63 |
- Maxkeys and Maxpasswd log to /tpm |
-
-
- MXS-57 |
- MaxScale should write a message to the error log when config is not found |
-
-
- MXS-54 |
- Write failed auth attempt to trace log |
-
-
- MXS-50 |
- Removing 1.0.5 RPM gives error about /etc/ld.so.conf.d/maxscale.conf |
-
-
- MXS-47 |
- Session freeze when small tail packet |
-
-
- MXS-5 |
- Possible memory leak in readwritesplit router |
-
-
- 736 |
- Memory leak while doing read/write splitting |
-
-
- 733 |
- Init-script deletes bin/maxscale |
-
-
- 732 |
- Build is broken: CentOS/RHEL 5 and SLES 11 |
-
-
- 730 |
- Regex filter and shorter than original replacement queries MaxScale |
-
-
- 729 |
- PDO prepared statements bug introduced in Maxscale 1.0.5 |
-
-
- 721 |
- Documentation suggests SIGTERM to re-read config file |
-
-
- 716 |
- $this->getReadConnection()->query('SET @id = 0;'); |
-
-
- 709 |
- "COPYRIGHT LICENSE README SETUP" files go to /usr/local/mariadb-maxscale/ after 'make package' |
-
-
- 704 |
- "make testall" returns success status (exit code 0) even on failures |
-
-
- 698 |
- Using invalid parameter in many maxadmin commands causes MaxScale to fail |
-
-
- 693 |
- Freeing tee filter's orphaned sessions causes a segfault when embedded server closes |
-
-
- 690 |
- CPU/architecture is hardcoded into debian/rules |
-
-
- 686 |
- TestService fails because of the modules used in it aren't meant for actual use |
-
-
- 677 |
- Race condition in tee filter clientReply |
-
-
- 676 |
- "Write to backend failed. Session closed." when changing default database via readwritesplit with max_slave_connections != 100% |
-
-
- 673 |
- MaxScale crashes if "Users table data" is empty and "show dbusers" is executed in maxadmin |
-
-
- 670 |
- Tee filter: statement router loses statements when other router gets enough ahead |
-
-
- 665 |
- Core: accessing freed memory when session is closed |
-
-
- 659 |
- MaxScale doesn't shutdown if none of the configured services start |
-
-
- 648 |
- use database is sent forever with tee filter to a readwrite split service |
-
-
- 620 |
- enable_root_user=true generates errors to error log |
-
-
- 612 |
- Service was started although no users could be loaded from database |
-
-
- 600 |
- RWSplit: if session command fails in some backend, it is not dropped from routing session |
-
-
- 587 |
- Hint filter don't work if listed before regex filter in configuration file |
-
-
- 579 |
- serviceStartProtocol test crashes |
-
-
- 506 |
- Don't write to shm/tmpfs by default without telling and without a way to override it |
-
-
- 503 |
- TOC in the bundled PDFs doesn't link to actual sections |
-
-
- 457 |
- Please provide a list of build dependencies for building MaxScale |
-
-
- 361 |
- file_exists() *modifies* the file it checks for??? |
-
-
- 338 |
- Log manager spread down feature is disabled |
-
-
- 159 |
- Memory leak. Dbusers are loaded into memory but not unloaded |
-
-
-
-
-## Known Issues
-
-There are a number bugs and known limitations within this version of MaxScale, the most serious of this are listed below.
-
-* The Read/Write Splitter is a little too strict when it receives errors from slave servers during execution of session commands. This can result in sessions being terminated in situation in which MaxScale could recover without terminating the sessions.
-
-* MaxScale can not manage authentication that uses wildcard matching in hostnames in the mysql.user table of the backend database. The only wildcards that can be used are in IP address entries.
-
-* When users have different passwords based on the host from which they connect MaxScale is unable to determine which password it should use to connect to the backend database. This results in failed connections and unusable usernames in MaxScale.
-
-* Service init script is missing after upgrade from 1.0 in RPM-based system. Can be fixed by reinstalling the package ('yum reinstall maxscale' or 'rpm -i --force /maxscale-1.1.rpm')
-
-* Binlog Router Plugin is compatible with MySQL 5.6
- Binlog Router Plugin currently does not work for MariaDB 5.5 and MariaDB 10.0
-
-* LONGBLOG are currently not supported.
-
-* Galera Cluster variables, such as @@wsrep_node_name, are not resolved by the embedded MariaDB parser.
-
-* The Database Firewall filter does not support multi-statements. Using them will result in an error being sent to the client.
-
-## Packaging
-
-Both RPM and Debian packages are available for MaxScale in addition to the tar based releases previously distributed we now provide
-
-* CentOS/RedHat 5
-
-* CentOS/RedHat 6
-
-* CentOS/RedHat 7
-
-* Debian 6
-
-* Debian 7
-
-* Ubuntu 12.04 LTS
-
-* Ubuntu 13.10
-
-* Ubuntu 14.04 LTS
-
-* Fedora 19
-
-* Fedora 20
-
-* OpenSuSE 13
-
-* SuSE Linux Enterprise 11
-
-* SuSE Linux Enterprise 12
diff --git a/Documentation/Release-Notes/MaxScale-1.1.1-Release-Notes.md b/Documentation/Release-Notes/MaxScale-1.1.1-Release-Notes.md
deleted file mode 100644
index 59bb3506e..000000000
--- a/Documentation/Release-Notes/MaxScale-1.1.1-Release-Notes.md
+++ /dev/null
@@ -1,94 +0,0 @@
-# MariaDB MaxScale 1.1.1 Release Notes
-
-## 1.1.1 GA
-
-MaxScale 1.1 is the current stable (GA) release of MaxScale. Version 1.1.1 is mainly a bug fix release introducing fixes, but also introduces some improvements to existing functionality.
-
-## New Features
-
-### Improved memory management options
-
-Readwritesplit and schemarouter now both support upper limits to session state modifying commands. They both also allow the complete disabling of the history, making the sessions consume the smallest amount of memory while still making sure all slaves keep identical session states.
-
-### Improved trace logging
-
-The process of the user authentication data retrieval is logged into the trace log and the readconnroute router also outputs more information into the trace log. This allows for easier problem detection and configuration tuning.
-
-### More informative output from maxkeys and maxpasswd
-
-Using the password functionality in MaxScale is now a lot easier. Both programs now produce verbose and exact error messages.
-
-## Bug Fixes
-
-Here is a list of bugs fixed since the release of the 1.1.0 version of MaxScale. The bug IDs are from the **[MariaDB Jira](https://jira.mariadb.org/)**.
-
-* [MXS-99](https://jira.mariadb.org/browse/MXS-99): /etc/init.d/maxscale reload doesn't do anything
-* [MXS-83](https://jira.mariadb.org/browse/MXS-83): linkage fails when system pcre library is recent
-* [MXS-112](https://jira.mariadb.org/browse/MXS-112): Disable saving of session commands in the readwritesplit and schemarouter modules
-* [MXS-114](https://jira.mariadb.org/browse/MXS-114): Disable recovery of disconnected slaves
-* [MXS-73](https://jira.mariadb.org/browse/MXS-73): MaxScale uses nearly 100% CPU
-* [MXS-36](https://jira.mariadb.org/browse/MXS-36): bugzillaId-671: wrong message if SHOW DATABASES privilege is missing
-* [MXS-39](https://jira.mariadb.org/browse/MXS-39): bugzillaId-731:Boolean configuration parameters accept inconsistent parameters
-* [MXS-64](https://jira.mariadb.org/browse/MXS-64): maxkeys and Maxpasswd do not produce informative error output
-* [MXS-25](https://jira.mariadb.org/browse/MXS-25): bugzillaId-656: MySQL Monitor: claims that Master is available after master failure
-* [MXS-82](https://jira.mariadb.org/browse/MXS-82): cmake warns when mariadb is compiled without mysql_release
-* [MXS-69](https://jira.mariadb.org/browse/MXS-69): dbfwfilter should be pessimistic about rule syntax errors
-* [MXS-98](https://jira.mariadb.org/browse/MXS-98): regexfilter log
-* [MXS-28](https://jira.mariadb.org/browse/MXS-28): bugzillaId-433: Logging don't include assert information
-* [MXS-75](https://jira.mariadb.org/browse/MXS-75): "wildcard" rule also blocks COUNT(*)
-* [MXS-118](https://jira.mariadb.org/browse/MXS-118): Two monitors loaded at the same time result into not working installation
-* [MXS-33](https://jira.mariadb.org/browse/MXS-33): bugzillaId-702: CLI: list services command shows negative values for the number of users of a service (Read Service).
-* [MXS-17](https://jira.mariadb.org/browse/MXS-17): bugzillaId-736: Memory leak while doing read/write splitting
-* [MXS-30](https://jira.mariadb.org/browse/MXS-30): bugzillaId-487: Buffer manager should not use pointer arithmetic on void*
-* [MXS-81](https://jira.mariadb.org/browse/MXS-81): cmake fails when init scripts are missing
-* [MXS-127](https://jira.mariadb.org/browse/MXS-127): disable_sescmd_history causes MaxScale to crash under load
-
-## Known Issues
-
-There are a number bugs and known limitations within this version of MaxScale, the most serious of these are listed below.
-
-* The Read/Write Splitter is a little too strict when it receives errors from slave servers during execution of session commands. This can result in sessions being terminated in situations from which MaxScale could recover without terminating the sessions.
-
-* MaxScale cannot manage authentication that uses wildcard matching in hostnames in the mysql.user table of the backend database. The only wildcards that can be used are in IP address entries.
-
-* When users have different passwords based on the host from which they connect MaxScale is unable to determine which password it should use to connect to the backend database. This results in failed connections and unusable usernames in MaxScale.
-
-* Binlog Router Plugin is compatible with MySQL 5.6
- Binlog Router Plugin currently does not work for MariaDB 5.5 and MariaDB 10.0
-
-
-* LONGBLOB are currently not supported.
-
-* Galera Cluster variables, such as @@wsrep_node_name, are not resolved by the embedded MariaDB parser.
-
-* The Database Firewall filter does not support multi-statements. Using them will result in an error being sent to the client.
-
-## Packaging
-
-Both RPM and Debian packages are available for MaxScale in addition to the tar based releases. Packages are now provided for:
-
-* CentOS/RedHat 5
-
-* CentOS/RedHat 6
-
-* CentOS/RedHat 7
-
-* Debian 6
-
-* Debian 7
-
-* Ubuntu 12.04 LTS
-
-* Ubuntu 14.04 LTS
-
-* Fedora 19
-
-* Fedora 20
-
-* Fedora 21
-
-* OpenSuSE 13
-
-* SuSE Linux Enterprise 11
-
-* SuSE Linux Enterprise 12
diff --git a/Documentation/Release-Notes/MaxScale-1.2.0-Release-Notes.md b/Documentation/Release-Notes/MaxScale-1.2.0-Release-Notes.md
deleted file mode 100644
index e2da82780..000000000
--- a/Documentation/Release-Notes/MaxScale-1.2.0-Release-Notes.md
+++ /dev/null
@@ -1,99 +0,0 @@
-# MariaDB MaxScale 1.2 Release Notes
-
-## 1.2 GA
-
-This document details the changes in version 1.2 since the release of the 1.1.1 GA Release of the MaxScale product.
-
-###***PLEASE NOTICE: MaxScale installation directories have changed in this version***
-The 1.2 version of MaxScale differs from previous versions in its installation layout. Please take great care when upgrading MaxScale from previous versions to version 1.2. An automatic upgrade will not work due to the severe changes in the installation layout.
-
-## New Features
-
-### Non-root MaxScale
-You can now run MaxScale as any user. The standard installation of a MaxScale package now creates the maxscale user and the maxscale group.
-
-### FHS-compliant installation
-The 1.2 version of MaxScale now complies to the Filesystem Hierarchy Standard. This means that MAXSCALE_HOME is no longer necessary and directories can be moved to different locations.
-
-A quick list of changes in installation directories and file names:
-
- * Binaries go into `/usr/bin`
- * Configuration files to `/etc` and the configuration file is now lower case: `maxscale.cnf`
- * Logs to `/var/log/maxscale`
- * The module and library directory have been combined into a single directory in `/usr/lib64/maxscale`. If you have custom modules please make sure they are located there.
- * Data directory is `/var/lib/maxscale`. This is the default location for MaxScale-specific data.
- * PID file can be found at `/var/run/maxscale`
-
-### Client side SSL encryption
-MaxScale now supports SSL/TLS encrypted connections to MaxScale.
-
-### Launchable scripts
-Now you can configure MaxScale monitor module to automatically launch a script when it detects change in the state of a backend server. The script can be any customer script defined by you to take diagnostic or reporting action. With this you can easily customize MaxScale's behavior.
-
-### Lsyncd configuration guide
-A new tutorial has been added which helps you keep MaxScale's configuration files in sync across multiple hosts. This allows for easier HA setups with MaxScale and guarantees up-to-date configuration files on all nodes. The tutorial can be found [here](../Tutorials/MaxScale-HA-with-lsyncd.md).
-
-## Bug fixes
-
-Here is a list of bugs fixed since the release of MaxScale 1.1.1.
-
- * [MXS-24](https://jira.mariadb.org/browse/MXS-24): bugzillaId-604: Module load path documentation issues ...
- * [MXS-40](https://jira.mariadb.org/browse/MXS-40): Display logged in users
- * [MXS-113](https://jira.mariadb.org/browse/MXS-113): MaxScale seems to fail if built against MariaDB 10.0 libraries
- * [MXS-116](https://jira.mariadb.org/browse/MXS-116): Do not run maxscale as root.
- * [MXS-117](https://jira.mariadb.org/browse/MXS-117): Allow configuration of the log file directory
- * [MXS-125](https://jira.mariadb.org/browse/MXS-125): inconsistency in maxkeys/maxpassword output and parameters
- * [MXS-128](https://jira.mariadb.org/browse/MXS-128): cyclic dependency utils -> log_manager -> utils
- * [MXS-136](https://jira.mariadb.org/browse/MXS-136): Check for MaxScale replication heartbeat table existence before creating
- * [MXS-137](https://jira.mariadb.org/browse/MXS-137): cannot get sql for queries with length >= 0x80
- * [MXS-139](https://jira.mariadb.org/browse/MXS-139): Schemarouter authentication for wildcard grants fails without optimize_wildcard
- * [MXS-140](https://jira.mariadb.org/browse/MXS-140): strip_db_esc does not work without auth_all_servers
- * [MXS-162](https://jira.mariadb.org/browse/MXS-162): Fix Incorrect info in Configuration Guide
- * [MXS-165](https://jira.mariadb.org/browse/MXS-165): Concurrency issue while incrementing sessions in qlafilter
- * [MXS-166](https://jira.mariadb.org/browse/MXS-166): Memory leak when creating a new event
- * [MXS-171](https://jira.mariadb.org/browse/MXS-171): Allow reads on master for readwritesplit
- * [MXS-176](https://jira.mariadb.org/browse/MXS-176): Missing dependencies in documentation
- * [MXS-179](https://jira.mariadb.org/browse/MXS-179): Keep configuration changes in synch across MaxScale Mate Nodes
- * [MXS-180](https://jira.mariadb.org/browse/MXS-180): MariaDB10 binlog router compatibilty
- * [MXS-181](https://jira.mariadb.org/browse/MXS-181): Poor performance on TCP connection due to Nagle's algoritm
- * [MXS-182](https://jira.mariadb.org/browse/MXS-182): SHOW SLAVE STATUS and maxadmin "show services" for binlog router needs updated when used with MariaDB 10 Master
- * [MXS-212](https://jira.mariadb.org/browse/MXS-212): Stopped services accept connections
- * [MXS-225](https://jira.mariadb.org/browse/MXS-225): RPM Debug build packages have no debugging symbols
- * [MXS-227](https://jira.mariadb.org/browse/MXS-227): Memory leak in Galera Monitor
- * [MXS-244](https://jira.mariadb.org/browse/MXS-244): Memory leak when using prepared statements without arguments
-
-## Known Issues and Limitations
-
-There are a number bugs and known limitations within this version of MaxScale, the most serious of this are listed below.
-
-* MaxScale can not manage authentication that uses wildcard matching in hostnames in the mysql.user table of the backend database. The only wildcards that can be used are in IP address entries.
-
-* When users have different passwords based on the host from which they connect MaxScale is unable to determine which password it should use to connect to the backend database. This results in failed connections and unusable usernames in MaxScale.
-
-* LONGBLOB are currently not supported.
-
-* Galera Cluster variables, such as @@wsrep_node_name, are not resolved by the embedded MariaDB parser.
-
-* The Database Firewall filter does not support multi-statements. Using them will result in an error being sent to the client.
-
-## Packaging
-
-Both RPM and Debian packages are available for MaxScale in addition to the tar based releases previously distributed we now provide
-
-* CentOS/RedHat 5
-
-* CentOS/RedHat 6
-
-* CentOS/RedHat 7
-
-* Debian 6
-
-* Debian 7
-
-* Ubuntu 12.04 LTS
-
-* Ubuntu 14.04 LTS
-
-* SuSE Linux Enterprise 11
-
-* SuSE Linux Enterprise 12
diff --git a/Documentation/Release-Notes/MaxScale-1.3.0-Release-Notes.md b/Documentation/Release-Notes/MaxScale-1.3.0-Release-Notes.md
deleted file mode 100644
index 9afe57729..000000000
--- a/Documentation/Release-Notes/MaxScale-1.3.0-Release-Notes.md
+++ /dev/null
@@ -1,267 +0,0 @@
-# MariaDB MaxScale 1.3 Release Notes
-
-This document describes the changes in release 1.3, when compared to
-release 1.2.1.
-
-## 1.3.0
-
-For any problems you encounter, please consider submitting a bug
-report at [Jira](https://jira.mariadb.org).
-
-## New Features
-
-### Persistent Connections
-
-MaxScale 1.3.0 introduces the concept of *Persistent Connections*. With
-that is meant that the connection from MaxScale to the backend server is
-not terminated even if the connection from the client to MaxScale is.
-If a client makes frequent short connections, there may be a benefit from
-using the *Persistent Connection* feature as it may reduce the time it
-takes from establishing a connection from the client through MaxScale to
-the backend server.
-
-**NOTE**: The persistent connections do not track session state. This means
-that changing the default database or modifying the session state will cause
-those changes to be active even for new connections. If you use queries with
-implicit databases or use connections with different client settings, you
-should take great care when using persistent connections.
-
-Additional information is available in the following document:
-* [Administration Tutorial](../Tutorials/Administration-Tutorial.md#persistent-connections)
-
-### Binlog Server
-
-There are new administrative commands: STOP SLAVE, START SLAVE, RESET SLAVE
-and CHANGE MASTER TO. The master server details are now provided by a
-master.ini file located in binlog directory and could be changed via
-CHANGE MASTER TO command issued via MySQL connection to MaxScale.
-
-Before migrating to 1.3.0 it is necessary to put a writable master.ini file
-into binlog directory, containing these parameters:
-
-```
-[binlog_configuration]
-master_host=127.0.0.1
-master_port=3308
-master_user=repl
-master_password=somepass
-filestem=repl-bin
-```
-
-Users may change parameters according to their configuration.
-
-**Note**: the "servers" parameter is no longer required in the service
-definition.
-
-Additional information is available in the following documents:
-* [Binlogrouter Tutorial](../Tutorials/Replication-Proxy-Binlog-Router-Tutorial.md)
-* [Upgrading Binlogrouter to 1.3](../Upgrading/Upgrading-BinlogRouter-To-Maxscale-1.3.md)
-* [Binlogrouter Documentation](../Routers/Binlogrouter.md)
-
-### Logging Changes
-
-Before 1.3, MaxScale logged data to four different log files; *error*,
-*message*, *trace* and *debug*. Complementary and/or alternatively, MaxScale
-could also log to syslog, in which case messages intended for the error and
-message file were logged there. What files were enabled and written to was
-controlled by entries in the MaxScale configuration file.
-
-This has now been changed so that MaxScale logs to a single
-file - *maxscale.log* - and each logged entry is prepended with *error*,
-*warning*, *notice*, *info* or *debug*, depending on the seriousness or
-priority of the message. The levels are the same as those of syslog.
-MaxScale is still capable of complementary or alternatively logging to syslog.
-
-What used to be logged to the *message* file is now logged as a *notice*
-message and what used to be written to the *trace* file, is logged as an
-*info* message.
-
-By default, *notice*, *warning* and *error* messages are logged, while
-*info* and *debug* messages are not. Exactly what kind of messages are
-logged can be controlled via the MaxScale configuration file, but enabling
-and disabling different kinds of messages can also be performed at runtime
-from maxadmin.
-
-Earlier, the *error* and *message* files were written to the filesystem,
-while the *trace* and *debug* files were written to shared memory. The
-one and only log file of MaxScale is now by default written to the filesystem.
-This will have performance implications if *info* and *debug* messages are
-enabled.
-
-If you want to retain the possibility of turning on *info* and *debug*
-messages, without it impacting the performance too much, the recommended
-approach is to add the following entries to the MaxScale configuration file:
-
-```
-[maxscale]
-syslog=1
-maxlog=0
-log_to_shm=1
-```
-
-This will have the effect of MaxScale creating the *maxscale.log* into
-shared memory, but not logging anything to it. However, all *notice*,
-*warning* and *error* messages will be logged to syslog.
-
-Then, if there is a need to turn on *info* messages that can be done via
-the maxadmin interface:
-
-```
-MaxScale> enable log-priority info
-MaxScale> enable maxlog
-```
-
-Note that *info* and *debug* messages are never logged to syslog.
-
-### PCRE2 integration
-
-MaxScale now uses the PCRE2 library for regular expressions. This has been
-integrated into the core configuration processing and most of the modules.
-The main module which uses this is the regexfilter which now fully supports
-the PCRE2 syntax with proper substitutions. For a closer look at how this
-differs from the POSIX regular expression syntax take a look at the
-[PCRE2 documentation](http://www.pcre.org/current/doc/html/pcre2syntax.html).
-
-**Please note**, that the substitution string follows different rules than
-the traditional substitution strings. The usual way of referring to capture
-groups in the substitution string is with the backslash character followed
-by the capture group reference e.g. `\1` but the PCRE2 library uses the dollar
-character followed by the group reference. To quote the PCRE2 native API manual:
-
-```
-In the replacement string, which is interpreted as a UTF string in UTF mode, and is checked for UTF validity unless the PCRE2_NO_UTF_CHECK option is set, a dollar character is an escape character that can specify the insertion of characters from capturing groups in the pattern. The following forms are recognized:
-
- $$ insert a dollar character
- $