{"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:10","modified_gmt":"2023-01-22T05:58:10","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

The maximum number of connections that PostgreSQL will allow, is controlled by the max_connections <\/a>parameter. By default this allows a maximum of one hundred connections:<\/p>\n\n\n

\npostgres=# show max_connections;\n max_connections \n-----------------\n 100\n(1 row)\n<\/pre><\/div>\n\n\n
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<\/a> parameter which, by default, is limited to three:<\/p>\n\n\n
\npostgres=# show superuser_reserved_connections;\n superuser_reserved_connections \n--------------------------------\n 3\n(1 row)\n<\/pre><\/div>\n\n\n
This means, that 97 connections are available to “normal” 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
\npostgres@debian11pg:\/home\/postgres\/ [150] psql -c "alter system set max_connections=1" \nALTER SYSTEM\npostgres@debian11pg:\/home\/postgres\/ [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
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
\npostgres@debian11pg:\/home\/postgres\/ [150] sed -i '\/^max_connections\/d' $PGDATA\/postgresql.auto.conf\npostgres@debian11pg:\/home\/postgres\/ [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
Are configuration which does make more sense is this:<\/p>\n\n\n
\npostgres@debian11pg:\/home\/postgres\/ [150] psql -c "alter system set max_connections=4"\npostgres@debian11pg:\/home\/postgres\/ [150] pg_ctl restart\npostgres@debian11pg:\/home\/postgres\/ [150] psql -c "show max_connections"\n max_connections \n-----------------\n 4\n(1 row)\n<\/pre><\/div>\n\n\n
This will allow one “normal” connection and three superuser connections, which easily can be verified:<\/p>\n\n\n
\npostgres@debian11pg:\/home\/postgres\/ [150] psql -c "create user u with password 'u' login"\nCREATE ROLE\npostgres@debian11pg:\/home\/postgres\/ [150] psql -U u postgres &amp;\n[1] 16639\npostgres@debian11pg:\/home\/postgres\/ [150] psql -U u postgres &amp;\n[2] 16641\n17:20:32 postgres@debian11pg:\/home\/postgres\/ [150] psql: error: connection to server on socket "\/tmp\/.s.PGSQL.5442" failed: FATAL:  remaining connection slots are reserved for no\n<\/pre><\/div>\n\n\n
Super user connections do still work, of course:<\/p>\n\n\n
\npostgres@debian11pg:\/home\/postgres\/ [150] psql\npsql (15.0)\nType "help" for help.\n\npostgres=# select count(*) from pg_stat_activity \n\n<\/pre><\/div>\n\n\n
This is how much control you have around connections up to PostgreSQL15. With PostgreSQL 16, you’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
\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
The new parameter is called reserved_connections, and it is disabled by default:<\/p>\n\n\n
\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
Granting that role to a user, setting the parameter and restarting the instance will give you the new feature:<\/p>\n\n\n
\npostgres=# create user u with login password 'u';\nCREATE ROLE\npostgres=# create user x with login password 'x';\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 "pg_log".\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
With this configuration user “x” will only be able to create one connection. Any additional connection request will fail:<\/p>\n\n\n
\npostgres@debian11pg:\/home\/postgres\/ [pgdev] psql -U x postgres &amp;\n[2] 17310\npostgres@debian11pg:\/home\/postgres\/ [pgdev] psql (16devel)\nType "help" for help.\n\n[2]+  Stopped                 psql -U x postgres\npostgres@debian11pg:\/home\/postgres\/ [pgdev] psql -U x postgres &amp;\n[3] 17312\npostgres@debian11pg:\/home\/postgres\/ [pgdev] psql: error: connection to server on socket "\/tmp\/.s.PGSQL.5432" failed: FATAL:  remaining connection slots are reserved for roles with privileges of pg_use_reserved_connections\n\n[3]   Exit 2                  psql -U x postgres\n<\/pre><\/div>\n\n\n
User “u” 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
\npostgres@debian11pg:\/home\/postgres\/ [pgdev] psql -U u postgres &amp;\n[3] 17318\npostgres@debian11pg:\/home\/postgres\/ [pgdev] psql (16devel)\nType "help" for help.\n\n\n\n[3]+  Stopped                 psql -U u postgres\npostgres@debian11pg:\/home\/postgres\/ [pgdev] psql -U u postgres &amp;\n[4] 17320\npostgres@debian11pg:\/home\/postgres\/ [pgdev] psql: error: connection to server on socket "\/tmp\/.s.PGSQL.5432" failed: FATAL:  remaining connection slots are reserved for superusers\n\n[4]   Exit 2                  psql -U u postgres\n<\/pre><\/div>\n\n\n
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":"
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, […]<\/p>\n","protected":false},"author":29,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229,198],"tags":[77],"type_dbi":[],"class_list":["post-21783","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","category-database-management","tag-postgresql"],"acf":[],"yoast_head":"\nPostgreSQL 16: reserved_connections - dbi 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, […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/postgresql-16-reserved_connections\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2023-01-22T05:58:09+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-01-22T05:58:10+00:00\" \/>\n<meta name=\"author\" content=\"Daniel Westermann\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@westermanndanie\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Daniel Westermann\" \/>\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\":\"Daniel Westermann\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"headline\":\"PostgreSQL 16: reserved_connections\",\"datePublished\":\"2023-01-22T05:58:09+00:00\",\"dateModified\":\"2023-01-22T05:58:10+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-16-reserved_connections\/\"},\"wordCount\":320,\"commentCount\":0,\"keywords\":[\"PostgreSQL\"],\"articleSection\":[\"Database Administration & Monitoring\",\"Database management\"],\"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 Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2023-01-22T05:58:09+00:00\",\"dateModified\":\"2023-01-22T05:58:10+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"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\":\"Accueil\",\"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 Blog\",\"description\":\"\",\"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\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\",\"name\":\"Daniel Westermann\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"caption\":\"Daniel Westermann\"},\"description\":\"Daniel Westermann is Principal Consultant and Technology Leader Open Infrastructure at dbi services. He has more than 15 years of experience in management, engineering and optimization of databases and infrastructures, especially on Oracle and PostgreSQL. Since the beginning of his career, he has specialized in Oracle Technologies and is Oracle Certified Professional 12c and Oracle Certified Expert RAC\/GridInfra. Over time, Daniel has become increasingly interested in open source technologies, becoming \u201cTechnology Leader Open Infrastructure\u201d and PostgreSQL expert. \u00a0Based on community or EnterpriseDB tools, he develops and installs complex high available solutions with PostgreSQL. He is also a certified PostgreSQL Plus 9.0 Professional and a Postgres Advanced Server 9.4 Professional. He is a regular speaker at PostgreSQL conferences in Switzerland and Europe. Today Daniel is also supporting our customers on AWS services such as AWS RDS, database migrations into the cloud, EC2 and automated infrastructure management with AWS SSM (System Manager). He is a certified AWS Solutions Architect Professional. Prior to dbi services, Daniel was Management System Engineer at LC SYSTEMS-Engineering AG in Basel. Before that, he worked as Oracle Developper &\u00a0Project Manager at Delta Energy Solutions AG in Basel (today Powel AG). Daniel holds a diploma in Business Informatics (DHBW, Germany). His branch-related experience mainly covers the pharma industry, the financial sector, energy, lottery and telecommunications.\",\"sameAs\":[\"https:\/\/x.com\/westermanndanie\"],\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/daniel-westermann\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"PostgreSQL 16: reserved_connections - dbi 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, […]","og_url":"https:\/\/www.dbi-services.com\/blog\/postgresql-16-reserved_connections\/","og_site_name":"dbi Blog","article_published_time":"2023-01-22T05:58:09+00:00","article_modified_time":"2023-01-22T05:58:10+00:00","author":"Daniel Westermann","twitter_card":"summary_large_image","twitter_creator":"@westermanndanie","twitter_misc":{"Written by":"Daniel Westermann","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":"Daniel Westermann","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"headline":"PostgreSQL 16: reserved_connections","datePublished":"2023-01-22T05:58:09+00:00","dateModified":"2023-01-22T05:58:10+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-16-reserved_connections\/"},"wordCount":320,"commentCount":0,"keywords":["PostgreSQL"],"articleSection":["Database Administration & Monitoring","Database management"],"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 Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2023-01-22T05:58:09+00:00","dateModified":"2023-01-22T05:58:10+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"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":"Accueil","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 Blog","description":"","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":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66","name":"Daniel Westermann","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","caption":"Daniel Westermann"},"description":"Daniel Westermann is Principal Consultant and Technology Leader Open Infrastructure at dbi services. He has more than 15 years of experience in management, engineering and optimization of databases and infrastructures, especially on Oracle and PostgreSQL. Since the beginning of his career, he has specialized in Oracle Technologies and is Oracle Certified Professional 12c and Oracle Certified Expert RAC\/GridInfra. Over time, Daniel has become increasingly interested in open source technologies, becoming \u201cTechnology Leader Open Infrastructure\u201d and PostgreSQL expert. \u00a0Based on community or EnterpriseDB tools, he develops and installs complex high available solutions with PostgreSQL. He is also a certified PostgreSQL Plus 9.0 Professional and a Postgres Advanced Server 9.4 Professional. He is a regular speaker at PostgreSQL conferences in Switzerland and Europe. Today Daniel is also supporting our customers on AWS services such as AWS RDS, database migrations into the cloud, EC2 and automated infrastructure management with AWS SSM (System Manager). He is a certified AWS Solutions Architect Professional. Prior to dbi services, Daniel was Management System Engineer at LC SYSTEMS-Engineering AG in Basel. Before that, he worked as Oracle Developper &\u00a0Project Manager at Delta Energy Solutions AG in Basel (today Powel AG). Daniel holds a diploma in Business Informatics (DHBW, Germany). His branch-related experience mainly covers the pharma industry, the financial sector, energy, lottery and telecommunications.","sameAs":["https:\/\/x.com\/westermanndanie"],"url":"https:\/\/www.dbi-services.com\/blog\/author\/daniel-westermann\/"}]}},"_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\/29"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=21783"}],"version-history":[{"count":15,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/21783\/revisions"}],"predecessor-version":[{"id":21881,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/21783\/revisions\/21881"}],"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"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=21783"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}