<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>High Availability on BonesMoses.org</title>
    <link>https://bonesmoses.org/tags/high-availability/</link>
    <description>Recent content in High Availability on BonesMoses.org</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 20 Dec 2024 12:26:38 -0600</lastBuildDate><atom:link href="https://bonesmoses.org/tags/high-availability/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PG Phriday: Kubernetes Killed the High Availability Star</title>
      <link>https://bonesmoses.org/2024/pg-phriday-kubernetes-killed-the-high-availability-star/</link>
      <pubDate>Fri, 20 Dec 2024 12:26:38 -0600</pubDate>
      
      <guid>https://bonesmoses.org/2024/pg-phriday-kubernetes-killed-the-high-availability-star/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://postgresconf.org/conferences/SEA2024&#34;&gt;Postgres Conference Seattle 2024&lt;/a&gt; partnered up with &lt;a href=&#34;https://passdatacommunitysummit.com&#34;&gt;PASS&lt;/a&gt; this year to present a united database front. They accepted my &amp;ldquo;&lt;a href=&#34;https://postgresconf.org/conferences/SEA2024/program/proposals/kubernetes-killed-the-high-availability-star-how-to-stop-worrying-and-embrace-postgres-in-the-cloud&#34;&gt;Kubernetes Killed the High Availability Star&lt;/a&gt;&amp;rdquo; talk, which I graciously gave on the last day of the conference. The next talk in that room wasn&amp;rsquo;t for another hour, so I had plenty of time to talk shop with attendees, about the future of Postgres, high availability, and Kubernetes in general.&lt;/p&gt;
&lt;p&gt;If you weren&amp;rsquo;t there and missed out on the fun, this is your chance to catch up and enjoy a few of my notorious bad puns along the way. Let me tell you why the concept of Postgres HA is dead.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>PG Phriday: Redefining Postgres High Availability</title>
      <link>https://bonesmoses.org/2024/pg-phriday-redefining-postgres-high-availability/</link>
      <pubDate>Fri, 15 Mar 2024 01:27:19 +0000</pubDate>
      
      <guid>https://bonesmoses.org/2024/pg-phriday-redefining-postgres-high-availability/</guid>
      <description>What is High Availability to Postgres? I&amp;rsquo;ve staked my career on the answer to that question since I first presented an HA stack to Postgres Open in 2012, and I still don&amp;rsquo;t feel like there&amp;rsquo;s an acceptable answer. No matter how the HA techniques have advanced since then, there&amp;rsquo;s always been a nagging suspicion in my mind that something is missing.
But I&amp;rsquo;m here to say that a bit of research has uncovered an approach that many different Postgres cloud vendors appear to be converging upon.</description>
    </item>
    
    <item>
      <title>PG Phriday: Sidewinder</title>
      <link>https://bonesmoses.org/2015/pg-phriday-sidewinder/</link>
      <pubDate>Fri, 06 Nov 2015 14:18:00 +0000</pubDate>
      
      <guid>https://bonesmoses.org/2015/pg-phriday-sidewinder/</guid>
      <description>Maintaining a Postgres database can involve a lot of busywork. This is especially true for more robust architectures that allocate at least one replica for failover purposes. It&amp;rsquo;s still fairly common for a DBA to create a replica to accommodate emergency or upgrade scenarios, only to have to repeat the process when it came time to revert to the original master system. It&amp;rsquo;s not safe to simply subscribe the original primary to the newly promoted secondary, so this leaves either creating a new clone, or using rsync to synchronize all of the files first.</description>
    </item>
    
    <item>
      <title>PG Phriday: Database Infrastructure</title>
      <link>https://bonesmoses.org/2015/pg-phriday-database-infrastructure/</link>
      <pubDate>Fri, 25 Sep 2015 12:07:41 +0000</pubDate>
      
      <guid>https://bonesmoses.org/2015/pg-phriday-database-infrastructure/</guid>
      <description>This PG Phriday is going to be a bit different. During my trip to Postgres Open this year, I attended a talk I had originally written off as &amp;ldquo;some Red Hat stuff.&amp;rdquo; But I saw the word &amp;ldquo;containers&amp;rdquo; in the PostgreSQL in Containers at Scale talk and became intrigued. A few days later, I had something of an epiphany: I&amp;rsquo;ve been wrong about servers for years; we all have.
That&amp;rsquo;s a pretty bold claim, so it needs some background.</description>
    </item>
    
    <item>
      <title>PG Phriday: High Availability Through Delayed Replication</title>
      <link>https://bonesmoses.org/2015/pg-phriday-high-availability-through-delayed-replication/</link>
      <pubDate>Fri, 27 Mar 2015 11:53:02 +0000</pubDate>
      
      <guid>https://bonesmoses.org/2015/pg-phriday-high-availability-through-delayed-replication/</guid>
      <description>High availability of PostgreSQL databases is incredibly important to me. You might even say it&amp;rsquo;s a special interest of mine. It&amp;rsquo;s one reason I&amp;rsquo;m both excited and saddened by a feature introduced in 9.4. I&amp;rsquo;m Excited because it&amp;rsquo;s a feature I plan to make extensive use of, and saddened because it has flown under the radar thus far. It&amp;rsquo;s not even listed in the What&amp;rsquo;s new in PostgreSQL 9.4 Wiki page.</description>
    </item>
    
    <item>
      <title>On PostgreSQL View Dependencies</title>
      <link>https://bonesmoses.org/2014/on-postgresql-view-dependencies/</link>
      <pubDate>Wed, 05 Nov 2014 17:20:41 +0000</pubDate>
      
      <guid>https://bonesmoses.org/2014/on-postgresql-view-dependencies/</guid>
      <description>As many seasoned DBAs might know, there&amp;rsquo;s one area that PostgreSQL still manages to be highly aggravating. By this, I mean the role views have in mucking up PostgreSQL dependencies. The part that annoys me personally, is that it doesn&amp;rsquo;t have to be this way.
Take, for example, what happens if you try to modify a VARCHAR column so that the column length is higher. We&amp;rsquo;re not changing the type, or dropping the column, or anything overly complicated.</description>
    </item>
    
    <item>
      <title>Finally Done With High Availability</title>
      <link>https://bonesmoses.org/2014/finally-done-with-high-availability/</link>
      <pubDate>Tue, 29 Jul 2014 15:23:42 +0000</pubDate>
      
      <guid>https://bonesmoses.org/2014/finally-done-with-high-availability/</guid>
      <description>Well, my publisher recently informed me that the book I&amp;rsquo;ve long been slaving over for almost a year, is finally finished. I must admit that PostgreSQL 9 High Availability Cookbook is somewhat awkward as a title, but that doesn&amp;rsquo;t detract from the contents. I&amp;rsquo;d like to discuss primarily why I wrote it.
When Packt first approached me in October of 2013, I was skeptical. I have to admit that I&amp;rsquo;m not a huge fan of the &amp;ldquo;cookbook&amp;rdquo; style they&amp;rsquo;ve been pushing lately.</description>
    </item>
    
  </channel>
</rss>
