{"id":41485,"date":"2025-11-11T10:32:57","date_gmt":"2025-11-11T09:32:57","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=41485"},"modified":"2025-11-11T10:32:59","modified_gmt":"2025-11-11T09:32:59","slug":"postgresql-19-the-wait-for-command","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/postgresql-19-the-wait-for-command\/","title":{"rendered":"PostgreSQL 19: The &#8220;WAIT FOR&#8221; command"},"content":{"rendered":"\n<p>When you go for replication and you don&#8217;t use synchronous replication there is always a window when data written on the primary is not yet available in the replica. This is known as &#8220;replication lag&#8221; and can be monitored using the <a href=\"https:\/\/www.postgresql.org\/docs\/current\/monitoring-stats.html#MONITORING-PG-STAT-REPLICATION-VIEW\">pg_stat_replication<\/a> catalog view. A recent <a href=\"https:\/\/git.postgresql.org\/gitweb\/?p=postgresql.git;a=commitdiff;h=447aae13b0305780e87cac7b0dd669db6fab3d9d\" target=\"_blank\" rel=\"noreferrer noopener\">commit<\/a> to PostgreSQL 19 implements a way to wait for data to be visible on the replica without switching to synchronous replication, and this is what the &#8220;WAIT FOR&#8221; command is for.<\/p>\n\n\n\n<p>Before we can see how that works we need a replica, because when you try to execute this command on a primary you&#8217;ll get this:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; highlight: [1,7]; title: ; notranslate\" title=\"\">\npostgres=# select version();\n                                        version                                        \n---------------------------------------------------------------------------------------\n PostgreSQL 19devel on x86_64-linux, compiled by gcc-15.1.1, 64-bit\n(1 row)\n\npostgres=# WAIT FOR LSN &#039;0\/306EE20&#039;;\nERROR:  recovery is not in progress\nHINT:  Waiting for the replay LSN can only be executed during recovery.\npostgres=# \n<\/pre><\/div>\n\n\n<p>So, let&#8217;s create a replica and start it up:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; highlight: [1,2,3,4,5,6]; title: ; notranslate\" title=\"\">\npostgres@:\/home\/postgres\/ &#x5B;pgdev] mkdir \/var\/tmp\/dummy\npostgres@:\/home\/postgres\/ &#x5B;pgdev] pg_basebackup --pgdata=\/var\/tmp\/dummy --write-recovery-conf --checkpoint=fast\npostgres@:\/home\/postgres\/ &#x5B;pgdev] echo &quot;port=8888&quot; &gt;&gt; \/var\/tmp\/dummy\/postgresql.auto.conf \npostgres@:\/home\/postgres\/ &#x5B;pgdev] chmod 700 \/var\/tmp\/dummy\npostgres@:\/home\/postgres\/ &#x5B;pgdev] pg_ctl --pgdata=\/var\/tmp\/dummy start\npostgres@:\/home\/postgres\/ &#x5B;pgdev] psql -p 8888 -c &quot;select pg_is_in_recovery()&quot;\n pg_is_in_recovery \n-------------------\n t\n(1 row)\n<\/pre><\/div>\n\n\n<p>As nothing is happening on the primary right now, data on the primary and the replica is exactly the same:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; highlight: [1]; title: ; notranslate\" title=\"\">\npostgres=# select usename,sent_lsn,write_lsn,flush_lsn,replay_lsn from pg_stat_replication;\n usename  |  sent_lsn  | write_lsn  | flush_lsn  | replay_lsn \n----------+------------+------------+------------+------------\n postgres | 0\/03000060 | 0\/03000060 | 0\/03000060 | 0\/03000060\n<\/pre><\/div>\n\n\n<p>To see how &#8220;WAIT FOR&#8221; behaves we need to a little cheating and pause WAL replaying on the replica (we could also cut the the network between the primary and the replica):<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: sql; highlight: [1,6]; title: ; notranslate\" title=\"\">\npostgres@:\/home\/postgres\/ &#x5B;pgdev] psql -p 8888 -c &quot;select * from pg_wal_replay_pause();&quot; \n pg_wal_replay_pause \n---------------------\n \n(1 row)\npostgres@:\/home\/postgres\/ &#x5B;pgdev] psql -p 8888 -c &quot;select * from pg_is_wal_replay_paused();&quot; \n pg_is_wal_replay_paused \n-------------------------\n t\n(1 row)\n<\/pre><\/div>\n\n\n<p>On the primary, create a table and get the current LSN:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; first-line: 1; highlight: [1,3,5]; title: ; notranslate\" title=\"\">\npostgres@:\/home\/postgres\/ &#x5B;pgdev] psql -c &quot;create table t(a int)&quot;\nCREATE TABLE\npostgres@:\/home\/postgres\/ &#x5B;pgdev] psql -c &quot;insert into t values(1)&quot;\nINSERT 0 1\npostgres@:\/home\/postgres\/ &#x5B;pgdev] psql -c &quot;select pg_current_wal_insert_lsn();&quot;\n pg_current_wal_insert_lsn \n---------------------------\n 0\/03018CA8\n(1 row)\n<\/pre><\/div>\n\n\n<p>As WAL replay on the replica is paused, the &#8220;WAIT FOR&#8221; command will now block:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; title: ; notranslate\" title=\"\">\npostgres@:\/home\/postgres\/ &#x5B;pgdev] psql -p 8888 -c &quot;WAIT FOR LSN &#039;0\/03018CA8&#039;&quot; \n<\/pre><\/div>\n\n\n<p>This is the intended behavior as we want to make sure that we can see all the data up to this LSN. Once we resume WAL replay on the replica the &#8220;WAIT FOR&#8221; command will return success as all the data reached the replica:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; highlight: [1]; title: ; notranslate\" title=\"\">\npostgres@:\/home\/postgres\/ &#x5B;DEV] psql -p 8888 -c &quot;select * from pg_wal_replay_resume();&quot;\n pg_wal_replay_resume \n----------------------\n \n(1 row)\n<\/pre><\/div>\n\n\n<p>&#8230; the other session will unblock:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; highlight: [1]; title: ; notranslate\" title=\"\">\npostgres@:\/home\/postgres\/ &#x5B;pgdev] psql -p 8888 -c &quot;WAIT FOR LSN &#039;0\/03018CA8&#039;&quot; \n status  \n---------\n success\n(1 row)\n<\/pre><\/div>\n\n\n<p>So, starting with PostgreSQL 19 next year, there is a way for applications to make sure that a replica reached all the data up to a specific LSN by blocking until the data is there.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When you go for replication and you don&#8217;t use synchronous replication there is always a window when data written on the primary is not yet available in the replica. This is known as &#8220;replication lag&#8221; and can be monitored using the pg_stat_replication catalog view. A recent commit to PostgreSQL 19 implements a way to wait [&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-41485","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 19: The &quot;WAIT FOR&quot; command - 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-19-the-wait-for-command\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"PostgreSQL 19: The &quot;WAIT FOR&quot; command\" \/>\n<meta property=\"og:description\" content=\"When you go for replication and you don&#8217;t use synchronous replication there is always a window when data written on the primary is not yet available in the replica. This is known as &#8220;replication lag&#8221; and can be monitored using the pg_stat_replication catalog view. A recent commit to PostgreSQL 19 implements a way to wait [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/postgresql-19-the-wait-for-command\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2025-11-11T09:32:57+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-11-11T09:32: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-19-the-wait-for-command\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-19-the-wait-for-command\\\/\"},\"author\":{\"name\":\"Daniel Westermann\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"headline\":\"PostgreSQL 19: The &#8220;WAIT FOR&#8221; command\",\"datePublished\":\"2025-11-11T09:32:57+00:00\",\"dateModified\":\"2025-11-11T09:32:59+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-19-the-wait-for-command\\\/\"},\"wordCount\":282,\"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-19-the-wait-for-command\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-19-the-wait-for-command\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-19-the-wait-for-command\\\/\",\"name\":\"PostgreSQL 19: The \\\"WAIT FOR\\\" command - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2025-11-11T09:32:57+00:00\",\"dateModified\":\"2025-11-11T09:32:59+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-19-the-wait-for-command\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-19-the-wait-for-command\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/postgresql-19-the-wait-for-command\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"PostgreSQL 19: The &#8220;WAIT FOR&#8221; command\"}]},{\"@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 19: The \"WAIT FOR\" command - 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-19-the-wait-for-command\/","og_locale":"en_US","og_type":"article","og_title":"PostgreSQL 19: The \"WAIT FOR\" command","og_description":"When you go for replication and you don&#8217;t use synchronous replication there is always a window when data written on the primary is not yet available in the replica. This is known as &#8220;replication lag&#8221; and can be monitored using the pg_stat_replication catalog view. A recent commit to PostgreSQL 19 implements a way to wait [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/postgresql-19-the-wait-for-command\/","og_site_name":"dbi Blog","article_published_time":"2025-11-11T09:32:57+00:00","article_modified_time":"2025-11-11T09:32: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-19-the-wait-for-command\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-19-the-wait-for-command\/"},"author":{"name":"Daniel Westermann","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"headline":"PostgreSQL 19: The &#8220;WAIT FOR&#8221; command","datePublished":"2025-11-11T09:32:57+00:00","dateModified":"2025-11-11T09:32:59+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-19-the-wait-for-command\/"},"wordCount":282,"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-19-the-wait-for-command\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-19-the-wait-for-command\/","url":"https:\/\/www.dbi-services.com\/blog\/postgresql-19-the-wait-for-command\/","name":"PostgreSQL 19: The \"WAIT FOR\" command - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2025-11-11T09:32:57+00:00","dateModified":"2025-11-11T09:32:59+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-19-the-wait-for-command\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/postgresql-19-the-wait-for-command\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-19-the-wait-for-command\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"PostgreSQL 19: The &#8220;WAIT FOR&#8221; command"}]},{"@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\/41485","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=41485"}],"version-history":[{"count":9,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/41485\/revisions"}],"predecessor-version":[{"id":41494,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/41485\/revisions\/41494"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=41485"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=41485"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=41485"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=41485"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}