{"id":27569,"date":"2023-09-04T13:17:17","date_gmt":"2023-09-04T11:17:17","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=27569"},"modified":"2023-09-04T14:43:59","modified_gmt":"2023-09-04T12:43:59","slug":"postgresql-17-allow-watch-to-stop-based-on-the-number-of-rows-returned","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/postgresql-17-allow-watch-to-stop-based-on-the-number-of-rows-returned\/","title":{"rendered":"PostgreSQL 17: Allow &#8220;\\watch&#8221; to stop based on the number of rows returned"},"content":{"rendered":"\n<p><a href=\"https:\/\/www.postgresql.org\/docs\/current\/app-psql.html\" target=\"_blank\" rel=\"noreferrer noopener\">psql<\/a> already is really powerful but still it gets more features with almost every release of PostgreSQL. One example is the &#8220;\\watch&#8221; meta command. This command was introduced in PostgreSQL 9.3 and hasn&#8217;t changed much since then. PostgreSQL 17, probably next year, will come with an extended &#8220;\\watch&#8221; meta command.<\/p>\n\n\n\n<p>Before we look at what was added lets briefly look at what &#8220;\\watch&#8221; is doing up to version 16 of PostgreSQL. This meta command always becomes handy when you want to monitor some progress of something in PostgreSQL, e.g. the number of active sessions:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; highlight: [1]; title: ; notranslate\" title=\"\">\npostgres=# select count(*) from pg_stat_activity where state = &#039;active&#039;;\n count \n-------\n     1\n(1 row)\n<\/pre><\/div>\n\n\n<p>Without the &#8220;\\watch&#8221; command you either have to repeat the query on your own, or you need to schedule it somehow. This is what &#8220;\\watch&#8221; is doing for you. Without any parameters &#8220;\\watch&#8221; will execute your last query every two seconds:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; highlight: [1]; title: ; notranslate\" title=\"\">\npostgres=# \\watch\nMon 04 Sep 2023 11:40:13 AM CEST (every 2s)\n\n count \n-------\n     1\n(1 row)\n\nMon 04 Sep 2023 11:40:15 AM CEST (every 2s)\n\n count \n-------\n     1\n(1 row)\n...\n<\/pre><\/div>\n\n\n<p>The amount of control you have up to PostgreSQL 16 is, that you can specify the internal:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; title: ; notranslate\" title=\"\">\npostgres=# \\watch 3\nMon 04 Sep 2023 11:41:35 AM CEST (every 3s)\n\n count \n-------\n     1\n(1 row)\n\nMon 04 Sep 2023 11:41:38 AM CEST (every 3s)\n\n count \n-------\n     1\n(1 row)\n<\/pre><\/div>\n\n\n<p>Starting with PostgreSQL 16 there will be an additional switch. You can tell &#8220;\\watch&#8221; to automatically stop executing after a given execution count is reached, e.g.<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; highlight: [1]; title: ; notranslate\" title=\"\">\npostgres=# \\watch interval=1 count=3\nMon 04 Sep 2023 11:47:42 AM CEST (every 1s)\n\n count \n-------\n     1\n(1 row)\n\nMon 04 Sep 2023 11:47:43 AM CEST (every 1s)\n\n count \n-------\n     1\n(1 row)\n\nMon 04 Sep 2023 11:47:44 AM CEST (every 1s)\n\n count \n-------\n     1\n(1 row)\n\n\npostgres=# \n\n<\/pre><\/div>\n\n\n<p>PostgreSQL 17 will bring an additional option: Stop executing when the query does not anymore return a certain amount of rows. For this we&#8217;ll need another session in the database:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; highlight: [2]; title: ; notranslate\" title=\"\">\n-- second session\npostgres=# select 1;\n ?column? \n----------\n        1\n(1 row)\n\npostgres=# \n\n<\/pre><\/div>\n\n\n<p>In the first session we ask for the database name of all sessions from the postgres user and tell &#8220;\\watch&#8221; to stop when that count goes below 3:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; highlight: [1,9]; title: ; notranslate\" title=\"\">\npostgres=# select datname from pg_stat_activity where usename = &#039;postgres&#039;;\n datname  \n----------\n \n postgres\n postgres\n(4 rows)\n\npostgres=# \\watch min_rows=3\nMon 04 Sep 2023 11:56:53 AM CEST (every 2s)\n\n datname  \n----------\n \n postgres\n postgres\n(3 rows)\n\nMon 04 Sep 2023 11:56:55 AM CEST (every 2s)\n\n datname  \n----------\n \n postgres\n postgres\n(3 rows)\n\n-- exit in the second session\n\nMon 04 Sep 2023 11:56:57 AM CEST (every 2s)\n\n datname  \n----------\n \n postgres\n(2 rows)\n\n<\/pre><\/div>\n\n\n<p>As soon as we exit the second session &#8220;\\watch&#8221; will stop as the number of rows returned drops to two. <\/p>\n","protected":false},"excerpt":{"rendered":"<p>psql already is really powerful but still it gets more features with almost every release of PostgreSQL. One example is the &#8220;\\watch&#8221; meta command. This command was introduced in PostgreSQL 9.3 and hasn&#8217;t changed much since then. PostgreSQL 17, probably next year, will come with an extended &#8220;\\watch&#8221; meta command. Before we look at what [&hellip;]<\/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-27569","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","category-database-management","tag-postgresql"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.4) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>PostgreSQL 17: Allow &quot;\\watch&quot; to stop based on the number of rows returned - 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-17-allow-watch-to-stop-based-on-the-number-of-rows-returned\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"PostgreSQL 17: Allow &quot;\\watch&quot; to stop based on the number of rows returned\" \/>\n<meta property=\"og:description\" content=\"psql already is really powerful but still it gets more features with almost every release of PostgreSQL. One example is the &#8220;watch&#8221; meta command. This command was introduced in PostgreSQL 9.3 and hasn&#8217;t changed much since then. PostgreSQL 17, probably next year, will come with an extended &#8220;watch&#8221; meta command. Before we look at what [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/postgresql-17-allow-watch-to-stop-based-on-the-number-of-rows-returned\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2023-09-04T11:17:17+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-09-04T12:43:59+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=\"2 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-17-allow-watch-to-stop-based-on-the-number-of-rows-returned\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-17-allow-watch-to-stop-based-on-the-number-of-rows-returned\\\/\"},\"author\":{\"name\":\"Daniel Westermann\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"headline\":\"PostgreSQL 17: Allow &#8220;\\\\watch&#8221; to stop based on the number of rows returned\",\"datePublished\":\"2023-09-04T11:17:17+00:00\",\"dateModified\":\"2023-09-04T12:43:59+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-17-allow-watch-to-stop-based-on-the-number-of-rows-returned\\\/\"},\"wordCount\":265,\"commentCount\":0,\"keywords\":[\"PostgreSQL\"],\"articleSection\":[\"Database Administration &amp; Monitoring\",\"Database management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-17-allow-watch-to-stop-based-on-the-number-of-rows-returned\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-17-allow-watch-to-stop-based-on-the-number-of-rows-returned\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-17-allow-watch-to-stop-based-on-the-number-of-rows-returned\\\/\",\"name\":\"PostgreSQL 17: Allow \\\"\\\\watch\\\" to stop based on the number of rows returned - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2023-09-04T11:17:17+00:00\",\"dateModified\":\"2023-09-04T12:43:59+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-17-allow-watch-to-stop-based-on-the-number-of-rows-returned\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-17-allow-watch-to-stop-based-on-the-number-of-rows-returned\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-17-allow-watch-to-stop-based-on-the-number-of-rows-returned\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"PostgreSQL 17: Allow &#8220;\\\\watch&#8221; to stop based on the number of rows returned\"}]},{\"@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 &amp;\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 17: Allow \"\\watch\" to stop based on the number of rows returned - 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-17-allow-watch-to-stop-based-on-the-number-of-rows-returned\/","og_locale":"en_US","og_type":"article","og_title":"PostgreSQL 17: Allow \"\\watch\" to stop based on the number of rows returned","og_description":"psql already is really powerful but still it gets more features with almost every release of PostgreSQL. One example is the &#8220;watch&#8221; meta command. This command was introduced in PostgreSQL 9.3 and hasn&#8217;t changed much since then. PostgreSQL 17, probably next year, will come with an extended &#8220;watch&#8221; meta command. Before we look at what [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/postgresql-17-allow-watch-to-stop-based-on-the-number-of-rows-returned\/","og_site_name":"dbi Blog","article_published_time":"2023-09-04T11:17:17+00:00","article_modified_time":"2023-09-04T12:43:59+00:00","author":"Daniel Westermann","twitter_card":"summary_large_image","twitter_creator":"@westermanndanie","twitter_misc":{"Written by":"Daniel Westermann","Est. reading time":"2 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-17-allow-watch-to-stop-based-on-the-number-of-rows-returned\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-17-allow-watch-to-stop-based-on-the-number-of-rows-returned\/"},"author":{"name":"Daniel Westermann","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"headline":"PostgreSQL 17: Allow &#8220;\\watch&#8221; to stop based on the number of rows returned","datePublished":"2023-09-04T11:17:17+00:00","dateModified":"2023-09-04T12:43:59+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-17-allow-watch-to-stop-based-on-the-number-of-rows-returned\/"},"wordCount":265,"commentCount":0,"keywords":["PostgreSQL"],"articleSection":["Database Administration &amp; Monitoring","Database management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/postgresql-17-allow-watch-to-stop-based-on-the-number-of-rows-returned\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-17-allow-watch-to-stop-based-on-the-number-of-rows-returned\/","url":"https:\/\/www.dbi-services.com\/blog\/postgresql-17-allow-watch-to-stop-based-on-the-number-of-rows-returned\/","name":"PostgreSQL 17: Allow \"\\watch\" to stop based on the number of rows returned - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2023-09-04T11:17:17+00:00","dateModified":"2023-09-04T12:43:59+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-17-allow-watch-to-stop-based-on-the-number-of-rows-returned\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/postgresql-17-allow-watch-to-stop-based-on-the-number-of-rows-returned\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-17-allow-watch-to-stop-based-on-the-number-of-rows-returned\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"PostgreSQL 17: Allow &#8220;\\watch&#8221; to stop based on the number of rows returned"}]},{"@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 &amp;\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\/27569","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=27569"}],"version-history":[{"count":5,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/27569\/revisions"}],"predecessor-version":[{"id":27584,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/27569\/revisions\/27584"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=27569"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=27569"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=27569"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=27569"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}