{"id":16803,"date":"2021-11-14T17:49:26","date_gmt":"2021-11-14T16:49:26","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/minor-postgresql-version-upgrades-in-a-patroni-cluster\/"},"modified":"2021-11-14T17:49:26","modified_gmt":"2021-11-14T16:49:26","slug":"minor-postgresql-version-upgrades-in-a-patroni-cluster","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/minor-postgresql-version-upgrades-in-a-patroni-cluster\/","title":{"rendered":"Minor PostgreSQL version upgrades in a Patroni cluster"},"content":{"rendered":"<p>Last week <a href=\"https:\/\/www.postgresql.org\/about\/news\/postgresql-141-135-129-1114-1019-and-9624-released-2349\/\" target=\"_blank\" rel=\"noopener\">PostgreSQL 14.1<\/a>, and all other minor versions for the supported version of PostgreSQL have been released. As usual, it is highly recommended to update to the latest minor release as soon as possible. Minor version updates of PostgreSQL are just a matter of installing the new binaries, shutting down the old cluster and starting it up again using the new binaries, that&#8217;s it. If you are using packages the procedure is to shutdown the cluster, install the new packages and start it up again. Nothing really complicated in either case and really easy to do. What we&#8217;ll look into in this post is, how you can do minor version PostgreSQL updates if you run <a href=\"https:\/\/github.com\/zalando\/patroni\/\" target=\"_blank\" rel=\"noopener\">Patroni<\/a> on top of PostgreSQL for implementing a high available solution.<\/p>\n<p><!--more--><\/p>\n<p>My current Patroni configuration looks like this:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\npostgres@patroni1:\/home\/postgres\/ [PG1] patronictl list\n+----------+-----------------+---------+---------+----+-----------+\n| Member   | Host            | Role    | State   | TL | Lag in MB |\n+ Cluster: postgres_ha (7030448849176438024) ----+----+-----------+\n| patroni1 | 192.168.100.170 | Leader  | running |  4 |           |\n| patroni2 | 192.168.100.171 | Replica | running |  4 |         0 |\n| patroni3 | 192.168.100.172 | Replica | running |  4 |         0 |\n+----------+-----------------+---------+---------+----+-----------+\n<\/pre>\n<p>There is a primary\/leader instance which feeds to replicas, all of them running PostgreSQL 14.0:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\npostgres@patroni1:\/home\/postgres\/ [PG1] psql -c \"select version()\";\n                                              version                                              \n---------------------------------------------------------------------------------------------------\n PostgreSQL 14.0 on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit\n(1 row)\n<\/pre>\n<p>What do we need to do to update this configuration to PostgreSQL 14.1? I&#8217;ve installed from source code, so the first step is to install the new version of PostgreSQL. This is already done in may case:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\npostgres@patroni1:\/home\/postgres\/ [PG1] ls -l \/u01\/app\/postgres\/product\/14\/\ntotal 8\ndrwxr-xr-x 6 postgres postgres 4096 Nov 10 20:43 db_0\ndrwxr-xr-x 6 postgres postgres 4096 Nov 11 15:35 db_1\n<\/pre>\n<p>&#8220;db_0&#8221; is PostgreSQL 14.0 and &#8220;db_1&#8221; is PostgreSQL 14.1. This is our standard, in your case this of course very probably looks different. Having both versions installed on all nodes already, what is the next step? First you need think about which node you want to upgrade first. We usually go for one of the replicas and in the case of <a href=\"https:\/\/www.postgresql.org\/docs\/14\/release-14-1.html#id-1.11.6.5.5\" target=\"_blank\" rel=\"noopener\">PostgreSQL 14.1 this is even recommended as one patch (&#8220;Fix physical replication for cases where the primary crashes after shipping a WAL segment that ends with a partial WAL record (\u00c1lvaro Herrera)&#8221;) should be applied on the replica first<\/a>.<\/p>\n<p>Let&#8217;s start with the third node (patroni3\/192.168.100.172). First we need to stop Patroni on that host:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\npostgres@patroni3:\/home\/postgres\/ [PG1] sudo systemctl stop patroni\n<\/pre>\n<p>Checking the Patroni status afterwards, we can see that the node is now gone:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\npostgres@patroni3:\/home\/postgres\/ [PG1] patronictl list\n+----------+-----------------+---------+---------+----+-----------+\n| Member   | Host            | Role    | State   | TL | Lag in MB |\n+ Cluster: postgres_ha (7030448849176438024) ----+----+-----------+\n| patroni1 | 192.168.100.170 | Leader  | running |  4 |           |\n| patroni2 | 192.168.100.171 | Replica | running |  4 |         0 |\n+----------+-----------------+---------+---------+----+-----------+\n<\/pre>\n<p>All we need to change is the path to the PostgreSQL binaries in the Patroni configuration file. Current I have this:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\npostgres@patroni3:\/home\/postgres\/ [PG1] grep bin_dir \/u01\/app\/postgres\/local\/dmk\/etc\/patroni.yml\n  bin_dir: \/u01\/app\/postgres\/product\/14\/db_0\/bin\n<\/pre>\n<p>&#8230; which points to my PostgreSQL 14.0 installation. After changing that:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\npostgres@patroni3:\/home\/postgres\/ [PG1] sed -i 's#14\/db_0#14\/db_1#g' \/u01\/app\/postgres\/local\/dmk\/etc\/patroni.yml\npostgres@patroni3:\/home\/postgres\/ [PG1] grep bin_dir \/u01\/app\/postgres\/local\/dmk\/etc\/patroni.yml\n  bin_dir: \/u01\/app\/postgres\/product\/14\/db_1\/bin\n<\/pre>\n<p>Once this is done, start the Patroni service and this replica is patched:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\npostgres@patroni3:\/home\/postgres\/ [PG1] sudo systemctl start patroni\npostgres@patroni3:\/home\/postgres\/ [PG1] psql -c \"select version()\"\n                                              version                                              \n---------------------------------------------------------------------------------------------------\n PostgreSQL 14.1 on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit\n(1 row)\n<\/pre>\n<p>Checking the status of the Patroni configuration the replica is back:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\npostgres@patroni3:\/home\/postgres\/ [PG1] patronictl list\n+----------+-----------------+---------+---------+----+-----------+\n| Member   | Host            | Role    | State   | TL | Lag in MB |\n+ Cluster: postgres_ha (7030448849176438024) ----+----+-----------+\n| patroni1 | 192.168.100.170 | Leader  | running |  4 |           |\n| patroni2 | 192.168.100.171 | Replica | running |  4 |         0 |\n| patroni3 | 192.168.100.172 | Replica | running |  4 |         0 |\n+----------+-----------------+---------+---------+----+-----------+\n<\/pre>\n<p>That was quite easy and you can follow the exact same steps for the second replica. If you prepare that well you&#8217;ll have a downtime of a few seconds per replica. The primary, as of now, did not have any downtime. This starts now and you have two choices: If you want that the primary stays on the same host, then you can disable auto failover in Patroni, patch the primary, bring it up again and finally enable auto failover. Another option is to switch the primary to another node, so the current primary becomes a new replica. Once roles are switched you can follow the procedure outlined above.<\/p>\n<p>We&#8217;ll do the switchover now:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\npostgres@patroni2:\/home\/postgres\/ [PG1] patronictl switchover\nMaster [patroni1]: patroni1\nCandidate ['patroni2', 'patroni3'] []: patroni2\nWhen should the switchover take place (e.g. 2021-11-14T19:45 )  [now]: now\nCurrent cluster topology\n+----------+-----------------+---------+---------+----+-----------+\n| Member   | Host            | Role    | State   | TL | Lag in MB |\n+ Cluster: postgres_ha (7030448849176438024) ----+----+-----------+\n| patroni1 | 192.168.100.170 | Leader  | running |  4 |           |\n| patroni2 | 192.168.100.171 | Replica | running |  4 |         0 |\n| patroni3 | 192.168.100.172 | Replica | running |  4 |         0 |\n+----------+-----------------+---------+---------+----+-----------+\nAre you sure you want to switchover cluster postgres_ha, demoting current master patroni1? [y\/N]: y\n\n2021-11-14 18:45:29.79070 Successfully switched over to \"patroni2\"\n+----------+-----------------+---------+---------+----+-----------+\n| Member   | Host            | Role    | State   | TL | Lag in MB |\n+ Cluster: postgres_ha (7030448849176438024) ----+----+-----------+\n| patroni1 | 192.168.100.170 | Replica | stopped |    |   unknown |\n| patroni2 | 192.168.100.171 | Leader  | running |  4 |           |\n| patroni3 | 192.168.100.172 | Replica | running |  4 |         0 |\n+----------+-----------------+---------+---------+----+-----------+\n\npostgres@patroni2:\/home\/postgres\/ [PG1] patronictl list\n+----------+-----------------+---------+---------+----+-----------+\n| Member   | Host            | Role    | State   | TL | Lag in MB |\n+ Cluster: postgres_ha (7030448849176438024) ----+----+-----------+\n| patroni1 | 192.168.100.170 | Replica | running |  5 |         0 |\n| patroni2 | 192.168.100.171 | Leader  | running |  5 |           |\n| patroni3 | 192.168.100.172 | Replica | running |  5 |         0 |\n+----------+-----------------+---------+---------+----+-----------+\n<\/pre>\n<p>Now we can follow the same procedure on the old primary:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">\npostgres@patroni1:\/home\/postgres\/ [PG1] hostname\npatroni1\npostgres@patroni1:\/home\/postgres\/ [PG1] sudo systemctl stop patroni\npostgres@patroni1:\/home\/postgres\/ [PG1] sed -i 's#14\/db_0#14\/db_1#g' \/u01\/app\/postgres\/local\/dmk\/etc\/patroni.yml\npostgres@patroni1:\/home\/postgres\/ [PG1] grep bin_dir \/u01\/app\/postgres\/local\/dmk\/etc\/patroni.yml\n  bin_dir: \/u01\/app\/postgres\/product\/14\/db_1\/bin\npostgres@patroni1:\/home\/postgres\/ [PG1] sudo systemctl start patroni\npostgres@patroni1:\/home\/postgres\/ [PG1] patronictl list\n+----------+-----------------+---------+---------+----+-----------+\n| Member   | Host            | Role    | State   | TL | Lag in MB |\n+ Cluster: postgres_ha (7030448849176438024) ----+----+-----------+\n| patroni1 | 192.168.100.170 | Replica | running |  5 |         0 |\n| patroni2 | 192.168.100.171 | Leader  | running |  5 |           |\n| patroni3 | 192.168.100.172 | Replica | running |  5 |         0 |\n+----------+-----------------+---------+---------+----+-----------+\npostgres@patroni1:\/home\/postgres\/ [PG1] psql -c \"select version()\";\n                                              version                                              \n---------------------------------------------------------------------------------------------------\n PostgreSQL 14.1 on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit\n(1 row)\n<\/pre>\n<p>All done.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Last week PostgreSQL 14.1, and all other minor versions for the supported version of PostgreSQL have been released. As usual, it is highly recommended to update to the latest minor release as soon as possible. Minor version updates of PostgreSQL are just a matter of installing the new binaries, shutting down the old cluster and [&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":[1543,77],"type_dbi":[],"class_list":["post-16803","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","tag-patroni","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>Minor PostgreSQL version upgrades in a Patroni cluster - 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\/minor-postgresql-version-upgrades-in-a-patroni-cluster\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Minor PostgreSQL version upgrades in a Patroni cluster\" \/>\n<meta property=\"og:description\" content=\"Last week PostgreSQL 14.1, and all other minor versions for the supported version of PostgreSQL have been released. As usual, it is highly recommended to update to the latest minor release as soon as possible. Minor version updates of PostgreSQL are just a matter of installing the new binaries, shutting down the old cluster and [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/minor-postgresql-version-upgrades-in-a-patroni-cluster\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2021-11-14T16:49: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=\"5 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\/minor-postgresql-version-upgrades-in-a-patroni-cluster\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/minor-postgresql-version-upgrades-in-a-patroni-cluster\/\"},\"author\":{\"name\":\"Daniel Westermann\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"headline\":\"Minor PostgreSQL version upgrades in a Patroni cluster\",\"datePublished\":\"2021-11-14T16:49:26+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/minor-postgresql-version-upgrades-in-a-patroni-cluster\/\"},\"wordCount\":506,\"commentCount\":0,\"keywords\":[\"Patroni\",\"PostgreSQL\"],\"articleSection\":[\"Database Administration &amp; Monitoring\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/minor-postgresql-version-upgrades-in-a-patroni-cluster\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/minor-postgresql-version-upgrades-in-a-patroni-cluster\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/minor-postgresql-version-upgrades-in-a-patroni-cluster\/\",\"name\":\"Minor PostgreSQL version upgrades in a Patroni cluster - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2021-11-14T16:49:26+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/minor-postgresql-version-upgrades-in-a-patroni-cluster\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/minor-postgresql-version-upgrades-in-a-patroni-cluster\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/minor-postgresql-version-upgrades-in-a-patroni-cluster\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Minor PostgreSQL version upgrades in a Patroni cluster\"}]},{\"@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":"Minor PostgreSQL version upgrades in a Patroni cluster - 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\/minor-postgresql-version-upgrades-in-a-patroni-cluster\/","og_locale":"en_US","og_type":"article","og_title":"Minor PostgreSQL version upgrades in a Patroni cluster","og_description":"Last week PostgreSQL 14.1, and all other minor versions for the supported version of PostgreSQL have been released. As usual, it is highly recommended to update to the latest minor release as soon as possible. Minor version updates of PostgreSQL are just a matter of installing the new binaries, shutting down the old cluster and [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/minor-postgresql-version-upgrades-in-a-patroni-cluster\/","og_site_name":"dbi Blog","article_published_time":"2021-11-14T16:49:26+00:00","author":"Daniel Westermann","twitter_card":"summary_large_image","twitter_creator":"@westermanndanie","twitter_misc":{"Written by":"Daniel Westermann","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/minor-postgresql-version-upgrades-in-a-patroni-cluster\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/minor-postgresql-version-upgrades-in-a-patroni-cluster\/"},"author":{"name":"Daniel Westermann","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"headline":"Minor PostgreSQL version upgrades in a Patroni cluster","datePublished":"2021-11-14T16:49:26+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/minor-postgresql-version-upgrades-in-a-patroni-cluster\/"},"wordCount":506,"commentCount":0,"keywords":["Patroni","PostgreSQL"],"articleSection":["Database Administration &amp; Monitoring"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/minor-postgresql-version-upgrades-in-a-patroni-cluster\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/minor-postgresql-version-upgrades-in-a-patroni-cluster\/","url":"https:\/\/www.dbi-services.com\/blog\/minor-postgresql-version-upgrades-in-a-patroni-cluster\/","name":"Minor PostgreSQL version upgrades in a Patroni cluster - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2021-11-14T16:49:26+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/minor-postgresql-version-upgrades-in-a-patroni-cluster\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/minor-postgresql-version-upgrades-in-a-patroni-cluster\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/minor-postgresql-version-upgrades-in-a-patroni-cluster\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Minor PostgreSQL version upgrades in a Patroni cluster"}]},{"@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\/16803","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=16803"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/16803\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=16803"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=16803"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=16803"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=16803"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}