{"id":21783,"date":"2023-01-22T06:58:09","date_gmt":"2023-01-22T05:58:09","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=21783"},"modified":"2023-01-22T06:58:09","modified_gmt":"2023-01-22T05:58:09","slug":"postgresql-16-reserved_connections","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/postgresql-16-reserved_connections\/","title":{"rendered":"PostgreSQL 16: reserved_connections"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">The maximum number of connections that PostgreSQL will allow, is controlled by the <a href=\"https:\/\/www.postgresql.org\/docs\/current\/runtime-config-connection.html#RUNTIME-CONFIG-CONNECTION-SETTINGS\">max_connections <\/a>parameter. By default this allows a maximum of one hundred connections:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; title: ; notranslate\" title=\"\">\npostgres=# show max_connections;\n max_connections \n-----------------\n 100\n(1 row)\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">In reality not one hundred connections are allowed for normal users, because some of those connections are reserved for superusers. This is controlled by the <a href=\"https:\/\/www.postgresql.org\/docs\/current\/runtime-config-connection.html#RUNTIME-CONFIG-CONNECTION-SETTINGS\" target=\"_blank\" rel=\"noreferrer noopener\">superuser_reserved_connections<\/a> parameter which, by default, is limited to three:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; title: ; notranslate\" title=\"\">\npostgres=# show superuser_reserved_connections;\n superuser_reserved_connections \n--------------------------------\n 3\n(1 row)\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">This means, that 97 connections are available to &#8220;normal&#8221; users. What happens if we set amount of available connections to one? With the default configuration of three (for superuser_reserved_connections) this seems to be somehow weird. Anyway, lets do it and see what happens:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; highlight: [1,3]; title: ; notranslate\" title=\"\">\npostgres@debian11pg:\/home\/postgres\/ &#x5B;150] psql -c &quot;alter system set max_connections=1&quot; \nALTER SYSTEM\npostgres@debian11pg:\/home\/postgres\/ &#x5B;150] pg_ctl restart\nwaiting for server to shut down.... done\nserver stopped\nwaiting for server to start....postgres: superuser_reserved_connections (3) must be less than max_connections (1)\n stopped waiting\npg_ctl: could not start server\nExamine the log output.\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">So, even if PostgreSQL allows us to set this, the instance will not start afterwards. Removing this configuration will allow us to start the instance again:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\npostgres@debian11pg:\/home\/postgres\/ &#x5B;150] sed -i &#039;\/^max_connections\/d&#039; $PGDATA\/postgresql.auto.conf\npostgres@debian11pg:\/home\/postgres\/ &#x5B;150] psql -l\n                                                 List of databases\n   Name    |  Owner   | Encoding |   Collate   |    Ctype    | ICU Locale | Locale Provider |   Access privileges   \n-----------+----------+----------+-------------+-------------+------------+-----------------+-----------------------\n postgres  | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 |            | libc            | \n template0 | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 |            | libc            | =c\/postgres          +\n           |          |          |             |             |            |                 | postgres=CTc\/postgres\n template1 | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 |            | libc            | =c\/postgres          +\n           |          |          |             |             |            |                 | postgres=CTc\/postgres\n(3 rows)\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">Are configuration which does make more sense is this:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\npostgres@debian11pg:\/home\/postgres\/ &#x5B;150] psql -c &quot;alter system set max_connections=4&quot;\npostgres@debian11pg:\/home\/postgres\/ &#x5B;150] pg_ctl restart\npostgres@debian11pg:\/home\/postgres\/ &#x5B;150] psql -c &quot;show max_connections&quot;\n max_connections \n-----------------\n 4\n(1 row)\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">This will allow one &#8220;normal&#8221; connection and three superuser connections, which easily can be verified:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\npostgres@debian11pg:\/home\/postgres\/ &#x5B;150] psql -c &quot;create user u with password &#039;u&#039; login&quot;\nCREATE ROLE\npostgres@debian11pg:\/home\/postgres\/ &#x5B;150] psql -U u postgres &amp;amp;\n&#x5B;1] 16639\npostgres@debian11pg:\/home\/postgres\/ &#x5B;150] psql -U u postgres &amp;amp;\n&#x5B;2] 16641\n17:20:32 postgres@debian11pg:\/home\/postgres\/ &#x5B;150] psql: error: connection to server on socket &quot;\/tmp\/.s.PGSQL.5442&quot; failed: FATAL:  remaining connection slots are reserved for no\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">Super user connections do still work, of course:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\npostgres@debian11pg:\/home\/postgres\/ &#x5B;150] psql\npsql (15.0)\nType &quot;help&quot; for help.\n\npostgres=# select count(*) from pg_stat_activity \n\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">This is how much control you have around connections up to PostgreSQL15. With PostgreSQL 16, you&#8217;ll have an additional option because a new parameter and a new role have been introduced. The new role is called pg_use_reserved_connections:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\npostgres=# select version();\n                                               version                                                \n------------------------------------------------------------------------------------------------------\n PostgreSQL 16devel on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit\n(1 row)\n\npostgres=# \\du *reserved*\n                     List of roles\n          Role name          |  Attributes  | Member of \n-----------------------------+--------------+-----------\n pg_use_reserved_connections | Cannot login | {}\n\npostgres=# \n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">The new parameter is called reserved_connections, and it is disabled by default:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\npostgres=# \\dconfig *reserved*\n    List of configuration parameters\n           Parameter            | Value \n--------------------------------+-------\n reserved_connections           | 0\n superuser_reserved_connections | 3\n(2 rows)\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">Granting that role to a user, setting the parameter and restarting the instance will give you the new feature:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; highlight: [1,3,5,7,9,11,18,24]; title: ; notranslate\" title=\"\">\npostgres=# create user u with login password &#039;u&#039;;\nCREATE ROLE\npostgres=# create user x with login password &#039;x&#039;;\nCREATE ROLE\npostgres=# grant pg_use_reserved_connections to u;\nGRANT ROLE\npostgres=# alter system set max_connections = 5;\nALTER SYSTEM\npostgres=# alter system set reserved_connections = 1;\nALTER SYSTEM\npostgres=# \\! pg_ctl restart\nwaiting for server to shut down.... done\nserver stopped\nwaiting for server to start....2023-01-22 06:46:41.828 CET - 1 - 17283 -  - @ - 0LOG:  redirecting log output to logging collector process\n2023-01-22 06:46:41.828 CET - 2 - 17283 -  - @ - 0HINT:  Future log output will appear in directory &quot;pg_log&quot;.\n done\nserver started\npostgres=# select 1;\nFATAL:  terminating connection due to administrator command\nserver closed the connection unexpectedly\n        This probably means the server terminated abnormally\n        before or while processing the request.\nThe connection to the server was lost. Attempting reset: Succeeded.\npostgres=# \\dconfig *connections*\n    List of configuration parameters\n           Parameter            | Value \n--------------------------------+-------\n log_connections                | off\n log_disconnections             | off\n max_connections                | 5\n reserved_connections           | 1\n superuser_reserved_connections | 3\n(5 rows)\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">With this configuration user &#8220;x&#8221; will only be able to create one connection. Any additional connection request will fail:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; highlight: [1,7]; title: ; notranslate\" title=\"\">\npostgres@debian11pg:\/home\/postgres\/ &#x5B;pgdev] psql -U x postgres &amp;amp;\n&#x5B;2] 17310\npostgres@debian11pg:\/home\/postgres\/ &#x5B;pgdev] psql (16devel)\nType &quot;help&quot; for help.\n\n&#x5B;2]+  Stopped                 psql -U x postgres\npostgres@debian11pg:\/home\/postgres\/ &#x5B;pgdev] psql -U x postgres &amp;amp;\n&#x5B;3] 17312\npostgres@debian11pg:\/home\/postgres\/ &#x5B;pgdev] psql: error: connection to server on socket &quot;\/tmp\/.s.PGSQL.5432&quot; failed: FATAL:  remaining connection slots are reserved for roles with privileges of pg_use_reserved_connections\n\n&#x5B;3]   Exit 2                  psql -U x postgres\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">User &#8220;u&#8221; will be able to create one connection, which comes from the reserved connections. Any additional connection request will fail as well, as the remaining slots are reserved for super users:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; highlight: [1,9]; title: ; notranslate\" title=\"\">\npostgres@debian11pg:\/home\/postgres\/ &#x5B;pgdev] psql -U u postgres &amp;amp;\n&#x5B;3] 17318\npostgres@debian11pg:\/home\/postgres\/ &#x5B;pgdev] psql (16devel)\nType &quot;help&quot; for help.\n\n\n\n&#x5B;3]+  Stopped                 psql -U u postgres\npostgres@debian11pg:\/home\/postgres\/ &#x5B;pgdev] psql -U u postgres &amp;amp;\n&#x5B;4] 17320\npostgres@debian11pg:\/home\/postgres\/ &#x5B;pgdev] psql: error: connection to server on socket &quot;\/tmp\/.s.PGSQL.5432&quot; failed: FATAL:  remaining connection slots are reserved for superusers\n\n&#x5B;4]   Exit 2                  psql -U u postgres\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">Nice, so in addition to reserving connection slots for super users, you can also do that for normal users if you configure the system accordingly. Starting with PostgreSQL 16, of course.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The maximum number of connections that PostgreSQL will allow, is controlled by the max_connections parameter. By default this allows a maximum of one hundred connections: In reality not one hundred connections are allowed for normal users, because some of those connections are reserved for superusers. This is controlled by the superuser_reserved_connections parameter which, by default,&hellip;&nbsp;<\/p>\n","protected":false},"author":28,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"neve_meta_sidebar":"","neve_meta_container":"","neve_meta_enable_content_width":"","neve_meta_content_width":0,"neve_meta_title_alignment":"","neve_meta_author_avatar":"","neve_post_elements_order":"","neve_meta_disable_header":"","neve_meta_disable_footer":"","neve_meta_disable_title":"","neve_meta_reading_time":"","_themeisle_gutenberg_block_has_review":false,"footnotes":""},"categories":[4133],"tags":[],"class_list":["post-21783","post","type-post","status-publish","format-standard","category-database"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.8 (Yoast SEO v28.8) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>PostgreSQL 16: reserved_connections - dbi services Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/postgresql-16-reserved_connections\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"PostgreSQL 16: reserved_connections\" \/>\n<meta property=\"og:description\" content=\"The maximum number of connections that PostgreSQL will allow, is controlled by the max_connections parameter. By default this allows a maximum of one hundred connections: In reality not one hundred connections are allowed for normal users, because some of those connections are reserved for superusers. This is controlled by the superuser_reserved_connections parameter which, by default,&hellip;&nbsp;\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/postgresql-16-reserved_connections\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi services Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/dbiservices\/\" \/>\n<meta property=\"article:published_time\" content=\"2023-01-22T05:58:09+00:00\" \/>\n<meta name=\"author\" content=\"Open source Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@dbiservices\" \/>\n<meta name=\"twitter:site\" content=\"@dbiservices\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Open source Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-16-reserved_connections\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-16-reserved_connections\\\/\"},\"author\":{\"name\":\"Open source Team\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/0b4548362cac3eeff8b3eaf329e3530a\"},\"headline\":\"PostgreSQL 16: reserved_connections\",\"datePublished\":\"2023-01-22T05:58:09+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-16-reserved_connections\\\/\"},\"wordCount\":320,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/#organization\"},\"articleSection\":[\"Database\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-16-reserved_connections\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-16-reserved_connections\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-16-reserved_connections\\\/\",\"name\":\"PostgreSQL 16: reserved_connections - dbi services Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2023-01-22T05:58:09+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-16-reserved_connections\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-16-reserved_connections\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-16-reserved_connections\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"PostgreSQL 16: reserved_connections\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\",\"name\":\"dbi services Blog\",\"description\":\"#BeSharing\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/#organization\",\"name\":\"dbi services\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/dbi-services-logo.png\",\"contentUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/dbi-services-logo.png\",\"width\":512,\"height\":512,\"caption\":\"dbi services\"},\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/dbiservices\\\/\",\"https:\\\/\\\/x.com\\\/dbiservices\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/dbi-services\\\/\",\"https:\\\/\\\/www.youtube.com\\\/user\\\/dbiservices\"],\"description\":\"Swiss IT consulting and services company specialized in efficient data infrastructures and platforms: databases, application servers, cloud, DevOps, digitalization, analytics, data quality and monitoring. Headquartered in Del\u00e9mont with offices in Nyon, Basel, Bern and Zurich.\",\"email\":\"info@dbi-services.com\",\"telephone\":\"+41 32 422 96 00\",\"legalName\":\"dbi services SA\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/0b4548362cac3eeff8b3eaf329e3530a\",\"name\":\"Open source Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/05\\\/open-source-author.png\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/05\\\/open-source-author.png\",\"contentUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/05\\\/open-source-author.png\",\"caption\":\"Open source Team\"},\"description\":\"Posts published under the Open source Team account are collective contributions by the dbi services open infrastructure consultants. The practice covers open-source databases and platforms, PostgreSQL first of all, along with MySQL, MariaDB, and Linux, from architecture, replication, and high availability to performance tuning and operations under service level agreements, and contributes actively to the PostgreSQL community.\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/open-source-team\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"PostgreSQL 16: reserved_connections - dbi services Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/postgresql-16-reserved_connections\/","og_locale":"en_US","og_type":"article","og_title":"PostgreSQL 16: reserved_connections","og_description":"The maximum number of connections that PostgreSQL will allow, is controlled by the max_connections parameter. By default this allows a maximum of one hundred connections: In reality not one hundred connections are allowed for normal users, because some of those connections are reserved for superusers. This is controlled by the superuser_reserved_connections parameter which, by default,&hellip;&nbsp;","og_url":"https:\/\/www.dbi-services.com\/blog\/postgresql-16-reserved_connections\/","og_site_name":"dbi services Blog","article_publisher":"https:\/\/www.facebook.com\/dbiservices\/","article_published_time":"2023-01-22T05:58:09+00:00","author":"Open source Team","twitter_card":"summary_large_image","twitter_creator":"@dbiservices","twitter_site":"@dbiservices","twitter_misc":{"Written by":"Open source Team","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-16-reserved_connections\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-16-reserved_connections\/"},"author":{"name":"Open source Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0b4548362cac3eeff8b3eaf329e3530a"},"headline":"PostgreSQL 16: reserved_connections","datePublished":"2023-01-22T05:58:09+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-16-reserved_connections\/"},"wordCount":320,"commentCount":0,"publisher":{"@id":"https:\/\/www.dbi-services.com\/#organization"},"articleSection":["Database"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/postgresql-16-reserved_connections\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-16-reserved_connections\/","url":"https:\/\/www.dbi-services.com\/blog\/postgresql-16-reserved_connections\/","name":"PostgreSQL 16: reserved_connections - dbi services Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2023-01-22T05:58:09+00:00","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-16-reserved_connections\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/postgresql-16-reserved_connections\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-16-reserved_connections\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"PostgreSQL 16: reserved_connections"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi services Blog","description":"#BeSharing","publisher":{"@id":"https:\/\/www.dbi-services.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.dbi-services.com\/#organization","name":"dbi services","url":"https:\/\/www.dbi-services.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2026\/09\/dbi-services-logo.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2026\/09\/dbi-services-logo.png","width":512,"height":512,"caption":"dbi services"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/dbiservices\/","https:\/\/x.com\/dbiservices","https:\/\/www.linkedin.com\/company\/dbi-services\/","https:\/\/www.youtube.com\/user\/dbiservices"],"description":"Swiss IT consulting and services company specialized in efficient data infrastructures and platforms: databases, application servers, cloud, DevOps, digitalization, analytics, data quality and monitoring. Headquartered in Del\u00e9mont with offices in Nyon, Basel, Bern and Zurich.","email":"info@dbi-services.com","telephone":"+41 32 422 96 00","legalName":"dbi services SA"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0b4548362cac3eeff8b3eaf329e3530a","name":"Open source Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2022\/05\/open-source-author.png","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2022\/05\/open-source-author.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2022\/05\/open-source-author.png","caption":"Open source Team"},"description":"Posts published under the Open source Team account are collective contributions by the dbi services open infrastructure consultants. The practice covers open-source databases and platforms, PostgreSQL first of all, along with MySQL, MariaDB, and Linux, from architecture, replication, and high availability to performance tuning and operations under service level agreements, and contributes actively to the PostgreSQL community.","url":"https:\/\/www.dbi-services.com\/blog\/author\/open-source-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/21783","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/28"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=21783"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/21783\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=21783"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=21783"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=21783"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}