{"id":12353,"date":"2019-04-09T09:44:24","date_gmt":"2019-04-09T07:44:24","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/postgresql-12-copying-replication-slots\/"},"modified":"2019-04-09T09:44:24","modified_gmt":"2019-04-09T07:44:24","slug":"postgresql-12-copying-replication-slots","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/postgresql-12-copying-replication-slots\/","title":{"rendered":"PostgreSQL 12: Copying replication slots"},"content":{"rendered":"<p>The concept of replication slots was introduced in PostgreSQL 9.4 and was created to prevent a primary instance to delete WAL that a replica still needs to apply. That could happen when you have a network interruption or the replica was down for another reason. With replication slots you can prevent that at the downside that your master could fill up your disk if the interruption is too long. This concept of a &#8220;physical replication slot&#8221; was then advanced so you can also create &#8220;logical replication slots&#8221; which are used in logical replication which made in into PostgreSQL 10. Now with PostgreSQL 12 being in active development another great feature made it into PostgreSQL core: Copying replication slots.<\/p>\n<p><!--more--><\/p>\n<p>What might that be good for? Lets assume the following scenario:<\/p>\n<ul>\n<li>You want to attach two replicas to your master instance<\/li>\n<li>You want both replicas to use a physical replication slot<\/li>\n<li>You want to build both replicas from the same basebackup and to start at the same position<\/li>\n<\/ul>\n<p>What you can do in PostgreSQL is to create base backup that will create a physical replication slot:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\npostgres@pgbox:\/home\/postgres\/ [PGDEV] psql -X -c \"select * from pg_replication_slots\" postgres\n slot_name | plugin | slot_type | datoid | database | temporary | active | active_pid | xmin | catalog_xmin | restart_lsn | confirmed_flush_lsn \n-----------+--------+-----------+--------+----------+-----------+--------+------------+------+--------------+-------------+---------------------\n(0 rows)\n\npostgres@pgbox:\/home\/postgres\/ [PGDEV] mkdir -p \/var\/tmp\/basebackup\npostgres@pgbox:\/home\/postgres\/ [PGDEV] pg_basebackup --create-slot --slot myslot --write-recovery-conf -D \/var\/tmp\/basebackup\/\npostgres@pgbox:\/home\/postgres\/ [PGDEV] psql -X -c \"select * from pg_replication_slots\" postgres\n slot_name | plugin | slot_type | datoid | database | temporary | active | active_pid | xmin | catalog_xmin | restart_lsn | confirmed_flush_lsn \n-----------+--------+-----------+--------+----------+-----------+--------+------------+------+--------------+-------------+---------------------\n myslot    |        | physical  |        |          | f         | f      |            |      |              | 0\/2000000   | \n(1 row)\n<\/pre>\n<p>(Please note that there is <a href=\"https:\/\/www.dbi-services.com\/blog\/no-more-recovery-conf-in-postgresql-12\/\" target=\"_blank\" rel=\"noopener noreferrer\">no more recovery.conf in PostgreSQL 12<\/a> so the recovery parameters have been added to postgresql.auto.conf)<\/p>\n<p>The replication slot will not be dropped after <a href=\"https:\/\/www.postgresql.org\/docs\/current\/app-pgbasebackup.html\" target=\"_blank\" rel=\"noopener noreferrer\">pg_basebackup<\/a> finished and you can use it to attach a new replica. But before doing that: As of PostgreSQL 12 you can copy the slot and then attach a second replica to the copied slot, so both replicas will start at the same position:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\npostgres@pgbox:\/home\/postgres\/ [PGDEV] psql -X -c \"select pg_copy_physical_replication_slot('myslot','myslot2')\" postgres\n pg_copy_physical_replication_slot \n-----------------------------------\n (myslot2,)\n(1 row)\n\npostgres@pgbox:\/home\/postgres\/ [PGDEV] psql -X -c \"select * from pg_replication_slots\" postgres\n slot_name | plugin | slot_type | datoid | database | temporary | active | active_pid | xmin | catalog_xmin | restart_lsn | confirmed_flush_lsn \n-----------+--------+-----------+--------+----------+-----------+--------+------------+------+--------------+-------------+---------------------\n myslot    |        | physical  |        |          | f         | f      |            |      |              | 0\/8000000   | \n myslot2   |        | physical  |        |          | f         | f      |            |      |              | 0\/8000000   | \n(2 rows)\n<\/pre>\n<p>As you can see both replication slots have the same value for &#8220;restart_lsn&#8221;. This will make it very easy to use the basebackup for the two replicas and start them from the same position:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\npostgres@pgbox:\/home\/postgres\/ [PGDEV] mkdir -p \/var\/tmp\/replica1\npostgres@pgbox:\/home\/postgres\/ [PGDEV] mkdir -p \/var\/tmp\/replica2\npostgres@pgbox:\/home\/postgres\/ [PGDEV] cp -pr \/var\/tmp\/basebackup\/* \/var\/tmp\/replica1\/\npostgres@pgbox:\/home\/postgres\/ [PGDEV] cp -pr \/var\/tmp\/basebackup\/* \/var\/tmp\/replica2\/\npostgres@pgbox:\/home\/postgres\/ [PGDEV] sed -i 's\/myslot\/myslot2\/g' \/var\/tmp\/replica2\/postgresql.auto.conf \npostgres@pgbox:\/home\/postgres\/ [PGDEV] echo \"port=8888\" &gt;&gt; \/var\/tmp\/replica1\/postgresql.auto.conf \npostgres@pgbox:\/home\/postgres\/ [PGDEV] echo \"port=8889\" &gt;&gt; \/var\/tmp\/replica2\/postgresql.auto.conf \npostgres@pgbox:\/home\/postgres\/ [PGDEV] chmod o-rwx \/var\/tmp\/replica1\npostgres@pgbox:\/home\/postgres\/ [PGDEV] chmod o-rwx \/var\/tmp\/replica2\n<\/pre>\n<p>What happened here:<\/p>\n<ul>\n<li>Restore the same basebackup to the new replica locations<\/li>\n<li>Change the slot to use for the second replica to our copied slot name<\/li>\n<li>Change the ports of both replicas because we are running on the same host<\/li>\n<li>Fix the permissions so pg_ctl will not complain<\/li>\n<\/ul>\n<p>That&#8217;s it. We can startup both replicas:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\npostgres@pgbox:\/home\/postgres\/ [PGDEV] pg_ctl -D \/var\/tmp\/replica1\/ start\npostgres@pgbox:\/home\/postgres\/ [PGDEV] pg_ctl -D \/var\/tmp\/replica2\/ start\npostgres@pgbox:\/home\/postgres\/ [PGDEV] psql -X -p 8888 -c \"select pg_is_in_recovery()\" postgres\n pg_is_in_recovery \n-------------------\n t\n(1 row)\n\npostgres@pgbox:\/home\/postgres\/ [PGDEV] psql -X -p 8889 -c \"select pg_is_in_recovery()\" postgres\n pg_is_in_recovery \n-------------------\n t\n(1 row)\n<\/pre>\n<p>Quite easy and we can confirm that both replicas are at the same location as previously:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\npostgres@pgbox:\/home\/postgres\/ [PGDEV] psql -X -c \"select * from pg_replication_slots\" postgres\n slot_name | plugin | slot_type | datoid | database | temporary | active | active_pid | xmin | catalog_xmin | restart_lsn | confirmed_flush_lsn \n-----------+--------+-----------+--------+----------+-----------+--------+------------+------+--------------+-------------+---------------------\n myslot    |        | physical  |        |          | f         | t      |      15622 |      |              | 0\/9000148   | \n myslot2   |        | physical  |        |          | f         | t      |      15632 |      |              | 0\/9000148   | \n(2 rows)\n<\/pre>\n<p>You can also copy logical replication slots, of course. Nice, thanks all involved.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The concept of replication slots was introduced in PostgreSQL 9.4 and was created to prevent a primary instance to delete WAL that a replica still needs to apply. That could happen when you have a network interruption or the replica was down for another reason. With replication slots you can prevent that at the downside [&hellip;]<\/p>\n","protected":false},"author":29,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229],"tags":[77,1601],"type_dbi":[],"class_list":["post-12353","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","tag-postgresql","tag-replication-slots"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.2) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>PostgreSQL 12: Copying replication slots - 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-12-copying-replication-slots\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"PostgreSQL 12: Copying replication slots\" \/>\n<meta property=\"og:description\" content=\"The concept of replication slots was introduced in PostgreSQL 9.4 and was created to prevent a primary instance to delete WAL that a replica still needs to apply. That could happen when you have a network interruption or the replica was down for another reason. With replication slots you can prevent that at the downside [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/postgresql-12-copying-replication-slots\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2019-04-09T07:44:24+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-12-copying-replication-slots\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-12-copying-replication-slots\/\"},\"author\":{\"name\":\"Daniel Westermann\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"headline\":\"PostgreSQL 12: Copying replication slots\",\"datePublished\":\"2019-04-09T07:44:24+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-12-copying-replication-slots\/\"},\"wordCount\":380,\"commentCount\":0,\"keywords\":[\"PostgreSQL\",\"replication slots\"],\"articleSection\":[\"Database Administration &amp; Monitoring\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/postgresql-12-copying-replication-slots\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-12-copying-replication-slots\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-12-copying-replication-slots\/\",\"name\":\"PostgreSQL 12: Copying replication slots - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2019-04-09T07:44:24+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-12-copying-replication-slots\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/postgresql-12-copying-replication-slots\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-12-copying-replication-slots\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"PostgreSQL 12: Copying replication slots\"}]},{\"@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 12: Copying replication slots - 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-12-copying-replication-slots\/","og_locale":"en_US","og_type":"article","og_title":"PostgreSQL 12: Copying replication slots","og_description":"The concept of replication slots was introduced in PostgreSQL 9.4 and was created to prevent a primary instance to delete WAL that a replica still needs to apply. That could happen when you have a network interruption or the replica was down for another reason. With replication slots you can prevent that at the downside [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/postgresql-12-copying-replication-slots\/","og_site_name":"dbi Blog","article_published_time":"2019-04-09T07:44:24+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-12-copying-replication-slots\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-12-copying-replication-slots\/"},"author":{"name":"Daniel Westermann","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"headline":"PostgreSQL 12: Copying replication slots","datePublished":"2019-04-09T07:44:24+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-12-copying-replication-slots\/"},"wordCount":380,"commentCount":0,"keywords":["PostgreSQL","replication slots"],"articleSection":["Database Administration &amp; Monitoring"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/postgresql-12-copying-replication-slots\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-12-copying-replication-slots\/","url":"https:\/\/www.dbi-services.com\/blog\/postgresql-12-copying-replication-slots\/","name":"PostgreSQL 12: Copying replication slots - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2019-04-09T07:44:24+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-12-copying-replication-slots\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/postgresql-12-copying-replication-slots\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-12-copying-replication-slots\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"PostgreSQL 12: Copying replication slots"}]},{"@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\/12353","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=12353"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/12353\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=12353"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=12353"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=12353"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=12353"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}