{"id":13010,"date":"2019-11-14T16:56:26","date_gmt":"2019-11-14T15:56:26","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/dealing-with-corrupted-system-indexes-in-postgresql\/"},"modified":"2019-11-14T16:56:26","modified_gmt":"2019-11-14T15:56:26","slug":"dealing-with-corrupted-system-indexes-in-postgresql","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/dealing-with-corrupted-system-indexes-in-postgresql\/","title":{"rendered":"Dealing with corrupted system indexes in PostgreSQL"},"content":{"rendered":"<p>This is something you do not want to see on an important PostgreSQL system:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\npostgres@centos8pg:\/home\/postgres\/ [pgdev] psql\npsql: error: could not connect to server: FATAL:  index \"pg_class_oid_index\" contains unexpected zero page at block 0\nHINT:  Please REINDEX it.\n<\/pre>\n<p>The hint is pretty clear on how you should fix this, but anyway, lets do a short demo on how to do it.<\/p>\n<p><!--more--><\/p>\n<p>There are various cases that could lead to corrupt indexes or tables in PostgreSQL: It could be PostgreSQL bug, of course. It could be an issue on the file system. It could also be caused by a power loss and your storage system somehow was not able to write the file(s) on disk anymore. <\/p>\n<p>For this little demo we&#8217;ll have a look at what indexes are available on the <a href=\"https:\/\/www.postgresql.org\/docs\/current\/catalog-pg-class.html\" target=\"_blank\" rel=\"noopener noreferrer\">pg_class<\/a> catalog table:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres=# select * from pg_indexes where tablename = 'pg_class';\n schemaname | tablename |             indexname             | tablespace |                                                    indexdef                                                    \n------------+-----------+-----------------------------------+------------+----------------------------------------------------------------------------------------------------------------\n pg_catalog | pg_class  | pg_class_oid_index                |            | CREATE UNIQUE INDEX pg_class_oid_index ON pg_catalog.pg_class USING btree (oid)\n pg_catalog | pg_class  | pg_class_relname_nsp_index        |            | CREATE UNIQUE INDEX pg_class_relname_nsp_index ON pg_catalog.pg_class USING btree (relname, relnamespace)\n pg_catalog | pg_class  | pg_class_tblspc_relfilenode_index |            | CREATE INDEX pg_class_tblspc_relfilenode_index ON pg_catalog.pg_class USING btree (reltablespace, relfilenode)\n<\/pre>\n<p>Taking the first one as an example lets corrupt the index by writing zeros to the beginning of the file on disk:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres=# select pg_relation_filepath('pg_class_oid_index');\n pg_relation_filepath \n----------------------\n base\/12710\/16386\n(1 row)\npostgres=# ! echo $PGDATA\n\/u02\/pgdata\/DEV\npostgres=# ! dd if=\/dev\/zero of=\/u02\/pgdata\/DEV\/base\/12710\/16386 bs=8k count=2\n2+0 records in\n2+0 records out\n16384 bytes (16 kB, 16 KiB) copied, 0.000226611 s, 72.3 MB\/s\n<\/pre>\n<p>What happens when we ask for something that should come from the index we just destroyed?<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres=# select oid from pg_class where oid = 123344;\nERROR:  could not read block 2 in file \"base\/12710\/16386\": read only 0 of 8192 bytes\n<\/pre>\n<p>This can&#8217;t obviously work so lets apply the fix that PostgreSQL recommended above and re-index the index:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres=# reindex index pg_class_oid_index;\nREINDEX\npostgres=# select oid from pg_class where oid = 123344;\n oid \n-----\n(0 rows)\n<\/pre>\n<p>After re-indexing (which completely re-writes the index) all is fine again. One issue with re-index is, that it blocks concurrent activity against the table. You might think that you can do this concurrently (which is not blocking) but this is not the case for system indexes:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres=# reindex index concurrently pg_class_oid_index;\nERROR:  cannot reindex system catalogs concurrently\n<\/pre>\n<p>So now we know how we can fix a corrupted index on a running system when we are already connected. A much worse situation would be this:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres=# select pg_relation_filepath('pg_class_oid_index');\n pg_relation_filepath \n----------------------\n base\/12710\/16389\n(1 row)\n\npostgres=# ! dd if=\/dev\/zero of=\/u02\/pgdata\/DEV\/base\/12710\/16389 bs=8k count=2\n2+0 records in\n2+0 records out\n16384 bytes (16 kB, 16 KiB) copied, 0.00029232 s, 56.0 MB\/s\npostgres=# q\n21:57:03 postgres@centos8pg:\/home\/postgres\/ [pgdev] pg_ctl restart -m fast\n<\/pre>\n<p>This is the same test as before (note that the file name changed as re-index has created a brand new index) but in addition PostgreSQL was restarted. Until now all seems fine as we did not see any issues when PostgreSQL started up, but:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres@centos8pg:\/home\/postgres\/ [pgdev] psql postgres\npsql: error: could not connect to server: FATAL:  index \"pg_class_oid_index\" contains unexpected zero page at block 0\nHINT:  Please REINDEX it.\n<\/pre>\n<p>You are not able to connect anymore so how can you re-index the corrupted index then? There is a parameter called <a href=\"https:\/\/www.postgresql.org\/docs\/current\/runtime-config-developer.html\" target=\"_blank\" rel=\"noopener noreferrer\">&#8220;ignore_system_indexes&#8221;<\/a> that you can use for this case. It tells PostgreSQL to ignore any indexes on system catalog tables.<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\npostgres@centos8pg:\/home\/postgres\/ [pgdev] echo \"ignore_system_indexes='true'\" &gt;&gt; $PGDATA\/postgresql.auto.conf\npostgres@centos8pg:\/home\/postgres\/ [pgdev] pg_ctl restart -m fast\n<\/pre>\n<p>Once this is set connections are possible again and you can apply the same fix:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\nostgres@centos8pg:\/home\/postgres\/ [pgdev] psql -X postgres\npsql (13devel)\nType \"help\" for help.\n\npostgres=# reindex index pg_class_oid_index;\nREINDEX\npostgres=# alter system set ignore_system_indexes = 'false';\nALTER SYSTEM\npostgres=# q\npostgres@centos8pg:\/home\/postgres\/ [pgdev] pg_ctl restart -m fast\n...\npostgres@centos8pg:\/home\/postgres\/ [pgdev] psql -X postgres\npsql (13devel)\nType \"help\" for help.\n\npostgres=# \n<\/pre>\n<p>Hopefully you&#8217;ll never see index corruption on system indexes in real life, but if you do, it is good to know the options for fixing it.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>This is something you do not want to see on an important PostgreSQL system: postgres@centos8pg:\/home\/postgres\/ [pgdev] psql psql: error: could not connect to server: FATAL: index &#8220;pg_class_oid_index&#8221; contains unexpected zero page at block 0 HINT: Please REINDEX it. The hint is pretty clear on how you should fix this, but anyway, lets do a short [&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],"type_dbi":[],"class_list":["post-13010","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","tag-postgresql"],"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>Dealing with corrupted system indexes in PostgreSQL - 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\/dealing-with-corrupted-system-indexes-in-postgresql\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Dealing with corrupted system indexes in PostgreSQL\" \/>\n<meta property=\"og:description\" content=\"This is something you do not want to see on an important PostgreSQL system: postgres@centos8pg:\/home\/postgres\/ [pgdev] psql psql: error: could not connect to server: FATAL: index &quot;pg_class_oid_index&quot; contains unexpected zero page at block 0 HINT: Please REINDEX it. The hint is pretty clear on how you should fix this, but anyway, lets do a short [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/dealing-with-corrupted-system-indexes-in-postgresql\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2019-11-14T15:56:26+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\/dealing-with-corrupted-system-indexes-in-postgresql\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dealing-with-corrupted-system-indexes-in-postgresql\/\"},\"author\":{\"name\":\"Daniel Westermann\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"headline\":\"Dealing with corrupted system indexes in PostgreSQL\",\"datePublished\":\"2019-11-14T15:56:26+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dealing-with-corrupted-system-indexes-in-postgresql\/\"},\"wordCount\":376,\"commentCount\":0,\"keywords\":[\"PostgreSQL\"],\"articleSection\":[\"Database Administration &amp; Monitoring\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/dealing-with-corrupted-system-indexes-in-postgresql\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dealing-with-corrupted-system-indexes-in-postgresql\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/dealing-with-corrupted-system-indexes-in-postgresql\/\",\"name\":\"Dealing with corrupted system indexes in PostgreSQL - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2019-11-14T15:56:26+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dealing-with-corrupted-system-indexes-in-postgresql\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/dealing-with-corrupted-system-indexes-in-postgresql\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dealing-with-corrupted-system-indexes-in-postgresql\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Dealing with corrupted system indexes in PostgreSQL\"}]},{\"@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":"Dealing with corrupted system indexes in PostgreSQL - 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\/dealing-with-corrupted-system-indexes-in-postgresql\/","og_locale":"en_US","og_type":"article","og_title":"Dealing with corrupted system indexes in PostgreSQL","og_description":"This is something you do not want to see on an important PostgreSQL system: postgres@centos8pg:\/home\/postgres\/ [pgdev] psql psql: error: could not connect to server: FATAL: index \"pg_class_oid_index\" contains unexpected zero page at block 0 HINT: Please REINDEX it. The hint is pretty clear on how you should fix this, but anyway, lets do a short [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/dealing-with-corrupted-system-indexes-in-postgresql\/","og_site_name":"dbi Blog","article_published_time":"2019-11-14T15:56:26+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\/dealing-with-corrupted-system-indexes-in-postgresql\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/dealing-with-corrupted-system-indexes-in-postgresql\/"},"author":{"name":"Daniel Westermann","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"headline":"Dealing with corrupted system indexes in PostgreSQL","datePublished":"2019-11-14T15:56:26+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/dealing-with-corrupted-system-indexes-in-postgresql\/"},"wordCount":376,"commentCount":0,"keywords":["PostgreSQL"],"articleSection":["Database Administration &amp; Monitoring"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/dealing-with-corrupted-system-indexes-in-postgresql\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/dealing-with-corrupted-system-indexes-in-postgresql\/","url":"https:\/\/www.dbi-services.com\/blog\/dealing-with-corrupted-system-indexes-in-postgresql\/","name":"Dealing with corrupted system indexes in PostgreSQL - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2019-11-14T15:56:26+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/dealing-with-corrupted-system-indexes-in-postgresql\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/dealing-with-corrupted-system-indexes-in-postgresql\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/dealing-with-corrupted-system-indexes-in-postgresql\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Dealing with corrupted system indexes in PostgreSQL"}]},{"@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\/13010","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=13010"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/13010\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=13010"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=13010"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=13010"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=13010"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}