How to Properly Close MySQL Connection Pools in PHP

In PHP web development, MySQL is the most common relational database, and using a connection pool can significantly improve performance by reusing open connections instead of creating a new one for each request.

A connection pool is a collection of pre‑opened database connections that the application can borrow and return, reducing the overhead of establishing connections repeatedly. MySQL provides functions for creating and closing these pooled connections.

Creating a Simple MySQL Connection

$conn = mysqli_connect($host, $user, $password, $database);

Here $host is the MySQL server hostname, $user the username, $password the password, and $database the target database.

After performing database operations, close the connection with: mysqli_close($conn); When using a connection pool, the workflow changes slightly: the pool is initialized when the application starts, and connections are fetched from the pool rather than created anew. After use, the connection should be returned to the pool instead of being closed directly.

Example of a Custom Connection‑Pool Class

// Create the pool
$pool = new mysqli_pool($host, $user, $password, $database);

// Get a connection
$conn = $pool->get_connection();

// ... perform database operations ...

// Return the connection to the pool
$pool->release_connection($conn);

The mysqli_pool class is a user‑defined pool. Its get_connection() method retrieves an available connection, while release_connection() returns the connection for reuse.

Automatic Cleanup with a Destructor

function __destruct() {
    $this->close_all_connections();
}

function close_all_connections() {
    foreach ($this->pool as $conn) {
        mysqli_close($conn);
    }
}

The __destruct() method is invoked automatically when the script finishes. It calls close_all_connections(), which iterates over every connection stored in the pool and closes each with mysqli_close(), ensuring that all resources are released.

In summary, correctly closing connections in a MySQL connection pool is crucial to avoid resource leaks and maintain application performance. By using a custom pool class and a destructor‑based cleanup, developers can manage acquisition and release of connections efficiently.