Bobcares

Adjusting max_connections in PostgreSQL

by | May 31, 2024

Learn how to adjust max_connections in PostgreSQL. Our PostgreSQL Support team is here to help you with your questions and concerns.

Adjusting max_connections in PostgreSQL

The `max_connections` parameter in PostgreSQL determines the maximum number of concurrent connections to the database server.

By default, this value is typically set to 100 connections, but it can be less if the system’s kernel settings do not support it. Before increasing this value, our experts recommend considering the application’s behavior and the system’s resources.

Adjusting max_connections in PostgreSQL

Increasing the `max_connections` parameter allows more clients to connect to the PostgreSQL server simultaneously. However, doing so without considering system resources can lead to CPU and I/O subsystem overloads. This can even degrade performance.

Steps to Adjust max_connections in PostgreSQL

  1. First, check the current value of the `max_connections` parameter:

    SHOW max_connections;

  2. Then, we can change the value of the `max_connections` parameter with the following command:

    ALTER SYSTEM SET max_connections = num_of_connections;

    Replace `num_of_connections` with the desired number of connections.

  3. Now, restart the PostgreSQL server to apply the changes.
    • On Windows:

      Open the “Services” application. Then, locate the “postgresql” service and restart it.

    • On Linux:

      Run one of the following commands:

      sudo service postgresql restart
      Or,
      sudo systemctl restart postgresql

  4. We can confirm that the new `max_connections` value has been applied by running:

    SHOW max_connections;

Optimizing Performance with shared_buffers

When increasing `max_connections`, our experts advise adjusting the `shared_buffers` parameter as well.

This setting decides how much memory PostgreSQL uses for shared memory buffers, which can impact performance.

We can use the `ALTER SYSTEM` command to set the `shared_buffers` parameter.

ALTER SYSTEM SET shared_buffers = buffer_size;

Replace `buffer_size` with the desired memory allocation.

Then, restart the PostgreSQL server again to apply this change.

Adjusting the `max_connections` parameter in PostgreSQL lets us handle more concurrent connections. Additionally, optimizing the `shared_buffers` parameter can further boost performance. With these steps, we can effectively manage and improve the PostgreSQL server’s capacity and performance.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In brief, our Support Experts demonstrated how to adjust max_connections in PostgreSQL.

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF