The INFORMATION_SCHEMA TP_THREAD_GROUP_STATE table now contains a CONNECT_THREAD_COUNT column that indicates the number of threads that are processing or waiting to process connection initialization and authentication. This enables the acceptor thread to handle new connections at a higher rate with reduced latency. To improve thread_pool plugin performance, connection authentication and initialization have been moved from the acceptor thread to the thread pool worker threads that handle client connections. For instructions, see Using the keyring_okv Oracle Key Vault Plugin. The keyring_okv keyring plugin now can use the SafeNet KeySecure Appliance as the KMIP back end for keyring storage. The keyring_okv plugin no longer supports RSA or DSA key types. This change does not affect the Oracle-produced MySQL Community build of MySQL Server, which uses the yaSSL library instead. The linked OpenSSL library for the MySQL Commercial Server has been updated to version 1.0.2k. INTO OUTFILE, for which NULL continues to be represented by N. This change does not affect text file import or export operations performed with LOAD DATA INFILE or SELECT. The use of N as a synonym for NULL in SQL statements is deprecated and is removed in MySQL 8.0. PROCEDURE ANALYSE() syntax is now deprecated and is removed in MySQL 8.0. The package is available at the Microsoft Download Center. Users should make sure the package has been installed on the system before starting the server.
Reminder: MySQL 5.7 requires the Microsoft Visual C++ 2013 Redistributable Package to run on Windows platforms.
The file (used to produce a default my-default.cnf or my-default.ini file) is no longer included in source distributions and my-default.cnf and my-default.ini are no longer included in or installed by distribution packages. To avoid potential race conditions, Debian packages now use the GNU install utility rather than a combination of mkdir, touch, and chown. Changes in RPM package structure require a larger set of packages to be removed to install MySQL Server cleanly. Support for DTrace is deprecated and is removed in MySQL 8.0. The -temp-pool server option is deprecated and will be removed in MySQL 8.0. The ENABLE_DEBUG_SYNC option has been removed and enabling WITH_DEBUG enables Debug Sync. MySQL failed to compile if -DENABLE_DEBUG_SYNC=OFF AND -DWITH_DEBUG=ON were both given. CMake support was added for compiling with Developer Studio 12.6.
Accordingly, there really isn't that much of a performance gain going from 32 to 64 bits with PostgreSQL on Windows the main tunable that would normally benefit from having more RAM available doesn't actually utilize it very well.- Windows builds now use the default runtime libraries (builds use the /MD flag).
You'll do better to leave the rest for the operating system cache rather than dedicate it to the database. The point of diminishing return generally ends up being <=512MB of dedicated memory for the database whether you have a 32-bit or 64-bit build of PostgreSQL. However, if you are on Windows, PostgreSQL doesn't handle shared memory as efficiently as on UNIX-ish platforms. The point of diminishing returns on that tunable (shared_buffers) is usually around 8GB, but it will be limited to <2GB on a 32-bit system. Second, it's possible to allocate more memory for the database's dedicated buffer cache. First, data types that can fit into 64-bits (larger integers and timestamp types mainly) can be more efficiently passed around directly in registers rather than using pointers. PostgreSQL benefits from having a 64-bit build in two main ways.