<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>SimplyBlock on BonesMoses.org</title>
		<link>https://bonesmoses.org/tags/simplyblock/</link>
		<description>Recent content in SimplyBlock on BonesMoses.org</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sun, 10 Nov 2024 17:41:56 -0600</lastBuildDate>
		
			<atom:link href="https://bonesmoses.org/tags/simplyblock/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Building Blocks and Stepping Stones</title>
				<link>https://bonesmoses.org/2024/building-blocks-and-stepping-stones/</link>
				<pubDate>Sun, 10 Nov 2024 17:41:56 -0600</pubDate>
				<guid>https://bonesmoses.org/2024/building-blocks-and-stepping-stones/</guid>
				<description>&lt;p&gt;Last week I attended &lt;a href=&#34;https://postgresconf.org/conferences/SEA2024&#34;&gt;Postgres Conference Seattle 2024&lt;/a&gt; as a speaker for two sessions. The first, titled &lt;a href=&#34;https://postgresconf.org/conferences/SEA2024/program/proposals/what-s-our-vector-victor&#34;&gt;&amp;ldquo;What&amp;rsquo;s our Vector, Victor?&amp;rdquo;&lt;/a&gt; discussed the merits of the &lt;a href=&#34;https://github.com/tembo-io/pg_vectorize&#34;&gt;pg_vectorize&lt;/a&gt; extension for Postgres. The second, titled &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;&amp;ldquo;Kubernetes Killed the High Availability Star&amp;rdquo;&lt;/a&gt; served an advocacy piece for the ultimate deprecation of Postgres High Availability tooling in general. On day two of the event, I ended up having a long conversation about system architecture with &lt;a href=&#34;https://www.linkedin.com/in/devhawk/&#34;&gt;Harry Pierson&lt;/a&gt; from &lt;a href=&#34;https://docs.dbos.dev&#34;&gt;DBOS&lt;/a&gt;.&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>&lt;p&gt;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 &lt;a href=&#34;https://bonesmoses.org/presentations/ha_postgres.pdf&#34;&gt;Postgres Open in 2012&lt;/a&gt;, and I &lt;em&gt;still&lt;/em&gt; 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.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
