{"id":11048,"date":"2018-03-29T14:11:39","date_gmt":"2018-03-29T12:11:39","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/insert-on-conflict-with-partitions-finally-works-in-postgresql-11\/"},"modified":"2018-03-29T14:11:39","modified_gmt":"2018-03-29T12:11:39","slug":"insert-on-conflict-with-partitions-finally-works-in-postgresql-11","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/insert-on-conflict-with-partitions-finally-works-in-postgresql-11\/","title":{"rendered":"Insert&#8230;on conflict with partitions finally works in PostgreSQL 11"},"content":{"rendered":"<p>Another partitioning improvement for PostgreSQL 11: <a href=\"https:\/\/www.postgresql.org\/docs\/current\/static\/sql-insert.html\" target=\"_blank\" rel=\"noopener\">Insert&#8230;on conflict<\/a> is now supported (for most cases) in PostgreSQL 11 thanks to this <a href=\"https:\/\/git.postgresql.org\/gitweb\/?p=postgresql.git;a=commit;h=555ee77a9668e3f1b03307055b5027e13bf1a715\" target=\"_blank\" rel=\"noopener\">commit<\/a>. Lets see how it works.<\/p>\n<p>We&#8217;ll again use the slightly modified little list partitioned table from the last post, here in PostgreSQL 10:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres=# select version();\n                                                          version                                       Insert                    \n----------------------------------------------------------------------------------------------------------------------------\n PostgreSQL 10.0 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-16), 64-bit\n(1 row)\n \npostgres=# create table part ( a int, b int, list varchar(5) ) partition by list (list);\nCREATE TABLE\npostgres=# create table part_1 partition of part for values in ('beer');\nCREATE TABLE\npostgres=# create table part_2 partition of part for values in ('wine');\nCREATE TABLE\npostgres=# create unique index iu1 on part_1 (a);\nCREATE INDEX\npostgres=# create unique index iu2 on part_2 (a);\nCREATE INDEX\npostgres=# d+ part\n                                          Table \"public.part\"\n Column |         Type         | Collation | Nullable | Default | Storage  | Stats target | Description \n--------+----------------------+-----------+----------+---------+----------+--------------+-------------\n a      | integer              |           |          |         | plain    |              | \n b      | integer              |           |          |         | plain    |              | \n list   | character varying(5) |           |          |         | extended |              | \nPartition key: LIST (list)\nPartitions: part_1 FOR VALUES IN ('beer'),\n            part_2 FOR VALUES IN ('wine')\n\npostgres=# d+ part_1\n                                         Table \"public.part_1\"\n Column |         Type         | Collation | Nullable | Default | Storage  | Stats target | Description \n--------+----------------------+-----------+----------+---------+----------+--------------+-------------\n a      | integer              |           |          |         | plain    |              | \n b      | integer              |           |          |         | plain    |              | \n list   | character varying(5) |           |          |         | extended |              | \nPartition of: part FOR VALUES IN ('beer')\nPartition constraint: ((list IS NOT NULL) AND ((list)::text = ANY (ARRAY['beer'::character varying(5)])))\nIndexes:\n    \"iu1\" UNIQUE, btree (a)\n\npostgres=# d+ part_2\n                                         Table \"public.part_2\"\n Column |         Type         | Collation | Nullable | Default | Storage  | Stats target | Description \n--------+----------------------+-----------+----------+---------+----------+--------------+-------------\n a      | integer              |           |          |         | plain    |              | \n b      | integer              |           |          |         | plain    |              | \n list   | character varying(5) |           |          |         | extended |              | \nPartition of: part FOR VALUES IN ('wine')\nPartition constraint: ((list IS NOT NULL) AND ((list)::text = ANY (ARRAY['wine'::character varying(5)])))\nIndexes:\n    \"iu2\" UNIQUE, btree (a)\n\n<\/pre>\n<p>Insert some sample data:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres=# insert into part(a,b,list) values (1,1,'beer');\nINSERT 0 1\npostgres=# insert into part(a,b,list) values (2,2,'beer');\nINSERT 0 1\npostgres=# select * from part;\n a | b | list \n---+---+------\n 1 | 1 | beer\n 2 | 2 | beer\n(2 rows)\n<\/pre>\n<p>When you try the following in PostgreSQL 10 it will fail:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres=# insert into part(a,b,list) values (1,2,'beer') on conflict (a) do update set b = 2;\nERROR:  ON CONFLICT clause is not supported with partitioned tables\n<\/pre>\n<p>Doing that directly on the partition is working:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres=# insert into part(a,b,list) values (1,2,'beer') on conflict (a) do update set b = 2;\nERROR:  ON CONFLICT clause is not supported with partitioned tables\npostgres=# insert into part_1(a,b,list) values (1,2,'beer') on conflict (a) do update set b = 2;\nINSERT 0 1\npostgres=# select * from part;\n a | b | list \n---+---+------\n 2 | 2 | beer\n 1 | 2 | beer\n(2 rows)\n<\/pre>\n<p>But who wants to do that directly on the partition? For sure this is a big limitation and not very useful. That got fixed now with PostgreSQL 11:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres=# select version();\n                                                  version                                                   \n------------------------------------------------------------------------------------------------------------\n PostgreSQL 11devel on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-16), 64-bit\n(1 row)\n\npostgres=# create table part ( a int, b int, list varchar(5) ) partition by list (list);\nCREATE TABLE\npostgres=# alter table part add constraint pk1 primary key (a,list);\nALTER TABLE\npostgres=# create table part_1 partition of part for values in ('beer');\nCREATE TABLE\npostgres=# create table part_2 partition of part for values in ('wine');\nCREATE TABLE\npostgres=# d+ part\n                                          Table \"public.part\"\n Column |         Type         | Collation | Nullable | Default | Storage  | Stats target | Description \n--------+----------------------+-----------+----------+---------+----------+--------------+-------------\n a      | integer              |           | not null |         | plain    |              | \n b      | integer              |           |          |         | plain    |              | \n list   | character varying(5) |           | not null |         | extended |              | \nPartition key: LIST (list)\nIndexes:\n    \"pk1\" PRIMARY KEY, btree (a, list)\nPartitions: part_1 FOR VALUES IN ('beer'),\n            part_2 FOR VALUES IN ('wine')\n\n\npostgres=# insert into part(a,b,list) values (1,1,'beer');\nINSERT 0 1\npostgres=# insert into part(a,b,list) values (2,2,'wine');\nINSERT 0 1\npostgres=# insert into part(a,b,list) values (1,2,'beer') on conflict (a,list) do update set b = 2;\nINSERT 0 1\n<\/pre>\n<p>Cool. But be aware that there still is a case which is not working:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">\npostgres=# select * from part;\n a | b | list \n---+---+------\n 1 | 2 | beer\n 2 | 2 | wine\n(2 rows)\n\npostgres=# insert into part(a,b,list) values (1,2,'beer') on conflict (a,list) do update set list='wine';\nERROR:  invalid ON UPDATE specification\nDETAIL:  The result tuple would appear in a different partition than the original tuple.\n<\/pre>\n<p>When you do an on conflict clause that would require to move the row into another partition (updating the partition key) it will fail.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Another partitioning improvement for PostgreSQL 11: Insert&#8230;on conflict is now supported (for most cases) in PostgreSQL 11 thanks to this commit. Lets see how it works. We&#8217;ll again use the slightly modified little list partitioned table from the last post, here in PostgreSQL 10: postgres=# select version(); version Insert &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;- PostgreSQL 10.0 on x86_64-pc-linux-gnu, compiled&hellip;&nbsp;<\/p>\n","protected":false},"author":28,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"neve_meta_sidebar":"","neve_meta_container":"","neve_meta_enable_content_width":"","neve_meta_content_width":0,"neve_meta_title_alignment":"","neve_meta_author_avatar":"","neve_post_elements_order":"","neve_meta_disable_header":"","neve_meta_disable_footer":"","neve_meta_disable_title":"","neve_meta_reading_time":"","_themeisle_gutenberg_block_has_review":false,"footnotes":""},"categories":[4133],"tags":[],"class_list":["post-11048","post","type-post","status-publish","format-standard","category-database"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.8 (Yoast SEO v28.8) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Insert...on conflict with partitions finally works in PostgreSQL 11 - dbi services 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\/insert-on-conflict-with-partitions-finally-works-in-postgresql-11\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Insert...on conflict with partitions finally works in PostgreSQL 11\" \/>\n<meta property=\"og:description\" content=\"Another partitioning improvement for PostgreSQL 11: Insert&#8230;on conflict is now supported (for most cases) in PostgreSQL 11 thanks to this commit. Lets see how it works. We&#8217;ll again use the slightly modified little list partitioned table from the last post, here in PostgreSQL 10: postgres=# select version(); version Insert ---------------------------------------------------------------------------------------------------------------------------- PostgreSQL 10.0 on x86_64-pc-linux-gnu, compiled&hellip;&nbsp;\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/insert-on-conflict-with-partitions-finally-works-in-postgresql-11\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi services Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/dbiservices\/\" \/>\n<meta property=\"article:published_time\" content=\"2018-03-29T12:11:39+00:00\" \/>\n<meta name=\"author\" content=\"Open source Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@dbiservices\" \/>\n<meta name=\"twitter:site\" content=\"@dbiservices\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Open source Team\" \/>\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\\\/insert-on-conflict-with-partitions-finally-works-in-postgresql-11\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/insert-on-conflict-with-partitions-finally-works-in-postgresql-11\\\/\"},\"author\":{\"name\":\"Open source Team\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/0b4548362cac3eeff8b3eaf329e3530a\"},\"headline\":\"Insert&#8230;on conflict with partitions finally works in PostgreSQL 11\",\"datePublished\":\"2018-03-29T12:11:39+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/insert-on-conflict-with-partitions-finally-works-in-postgresql-11\\\/\"},\"wordCount\":139,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/#organization\"},\"articleSection\":[\"Database\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/insert-on-conflict-with-partitions-finally-works-in-postgresql-11\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/insert-on-conflict-with-partitions-finally-works-in-postgresql-11\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/insert-on-conflict-with-partitions-finally-works-in-postgresql-11\\\/\",\"name\":\"Insert...on conflict with partitions finally works in PostgreSQL 11 - dbi services Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2018-03-29T12:11:39+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/insert-on-conflict-with-partitions-finally-works-in-postgresql-11\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/insert-on-conflict-with-partitions-finally-works-in-postgresql-11\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/insert-on-conflict-with-partitions-finally-works-in-postgresql-11\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Insert&#8230;on conflict with partitions finally works in PostgreSQL 11\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\",\"name\":\"dbi services Blog\",\"description\":\"#BeSharing\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/#organization\"},\"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\":\"Organization\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/#organization\",\"name\":\"dbi services\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/dbi-services-logo.png\",\"contentUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/dbi-services-logo.png\",\"width\":512,\"height\":512,\"caption\":\"dbi services\"},\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/dbiservices\\\/\",\"https:\\\/\\\/x.com\\\/dbiservices\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/dbi-services\\\/\",\"https:\\\/\\\/www.youtube.com\\\/user\\\/dbiservices\"],\"description\":\"Swiss IT consulting and services company specialized in efficient data infrastructures and platforms: databases, application servers, cloud, DevOps, digitalization, analytics, data quality and monitoring. Headquartered in Del\u00e9mont with offices in Nyon, Basel, Bern and Zurich.\",\"email\":\"info@dbi-services.com\",\"telephone\":\"+41 32 422 96 00\",\"legalName\":\"dbi services SA\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/0b4548362cac3eeff8b3eaf329e3530a\",\"name\":\"Open source Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/05\\\/open-source-author.png\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/05\\\/open-source-author.png\",\"contentUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/05\\\/open-source-author.png\",\"caption\":\"Open source Team\"},\"description\":\"Posts published under the Open source Team account are collective contributions by the dbi services open infrastructure consultants. The practice covers open-source databases and platforms, PostgreSQL first of all, along with MySQL, MariaDB, and Linux, from architecture, replication, and high availability to performance tuning and operations under service level agreements, and contributes actively to the PostgreSQL community.\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/open-source-team\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Insert...on conflict with partitions finally works in PostgreSQL 11 - dbi services 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\/insert-on-conflict-with-partitions-finally-works-in-postgresql-11\/","og_locale":"en_US","og_type":"article","og_title":"Insert...on conflict with partitions finally works in PostgreSQL 11","og_description":"Another partitioning improvement for PostgreSQL 11: Insert&#8230;on conflict is now supported (for most cases) in PostgreSQL 11 thanks to this commit. Lets see how it works. We&#8217;ll again use the slightly modified little list partitioned table from the last post, here in PostgreSQL 10: postgres=# select version(); version Insert ---------------------------------------------------------------------------------------------------------------------------- PostgreSQL 10.0 on x86_64-pc-linux-gnu, compiled&hellip;&nbsp;","og_url":"https:\/\/www.dbi-services.com\/blog\/insert-on-conflict-with-partitions-finally-works-in-postgresql-11\/","og_site_name":"dbi services Blog","article_publisher":"https:\/\/www.facebook.com\/dbiservices\/","article_published_time":"2018-03-29T12:11:39+00:00","author":"Open source Team","twitter_card":"summary_large_image","twitter_creator":"@dbiservices","twitter_site":"@dbiservices","twitter_misc":{"Written by":"Open source Team","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/insert-on-conflict-with-partitions-finally-works-in-postgresql-11\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/insert-on-conflict-with-partitions-finally-works-in-postgresql-11\/"},"author":{"name":"Open source Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0b4548362cac3eeff8b3eaf329e3530a"},"headline":"Insert&#8230;on conflict with partitions finally works in PostgreSQL 11","datePublished":"2018-03-29T12:11:39+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/insert-on-conflict-with-partitions-finally-works-in-postgresql-11\/"},"wordCount":139,"commentCount":0,"publisher":{"@id":"https:\/\/www.dbi-services.com\/#organization"},"articleSection":["Database"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/insert-on-conflict-with-partitions-finally-works-in-postgresql-11\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/insert-on-conflict-with-partitions-finally-works-in-postgresql-11\/","url":"https:\/\/www.dbi-services.com\/blog\/insert-on-conflict-with-partitions-finally-works-in-postgresql-11\/","name":"Insert...on conflict with partitions finally works in PostgreSQL 11 - dbi services Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2018-03-29T12:11:39+00:00","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/insert-on-conflict-with-partitions-finally-works-in-postgresql-11\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/insert-on-conflict-with-partitions-finally-works-in-postgresql-11\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/insert-on-conflict-with-partitions-finally-works-in-postgresql-11\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Insert&#8230;on conflict with partitions finally works in PostgreSQL 11"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi services Blog","description":"#BeSharing","publisher":{"@id":"https:\/\/www.dbi-services.com\/#organization"},"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":"Organization","@id":"https:\/\/www.dbi-services.com\/#organization","name":"dbi services","url":"https:\/\/www.dbi-services.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2026\/09\/dbi-services-logo.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2026\/09\/dbi-services-logo.png","width":512,"height":512,"caption":"dbi services"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/dbiservices\/","https:\/\/x.com\/dbiservices","https:\/\/www.linkedin.com\/company\/dbi-services\/","https:\/\/www.youtube.com\/user\/dbiservices"],"description":"Swiss IT consulting and services company specialized in efficient data infrastructures and platforms: databases, application servers, cloud, DevOps, digitalization, analytics, data quality and monitoring. Headquartered in Del\u00e9mont with offices in Nyon, Basel, Bern and Zurich.","email":"info@dbi-services.com","telephone":"+41 32 422 96 00","legalName":"dbi services SA"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0b4548362cac3eeff8b3eaf329e3530a","name":"Open source Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2022\/05\/open-source-author.png","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2022\/05\/open-source-author.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2022\/05\/open-source-author.png","caption":"Open source Team"},"description":"Posts published under the Open source Team account are collective contributions by the dbi services open infrastructure consultants. The practice covers open-source databases and platforms, PostgreSQL first of all, along with MySQL, MariaDB, and Linux, from architecture, replication, and high availability to performance tuning and operations under service level agreements, and contributes actively to the PostgreSQL community.","url":"https:\/\/www.dbi-services.com\/blog\/author\/open-source-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/11048","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\/28"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=11048"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/11048\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=11048"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=11048"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=11048"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}