<story><title>Implementing system-versioned tables in Postgres</title><url>https://hypirion.com/musings/implementing-system-versioned-tables-in-postgres</url></story><parent_chain><item><author>adamcharnock</author><text>&amp;gt; Now, there are extensions out there that implement versioning – temporal_tables being the most popular I think – but none are supported for managed Postgres instances on e.g. Azure or AWS. This means that if we want system-versioned tables, we’re forced to make it ourselves.&lt;p&gt;This really provokes a wild geek rage inside me. Not that it is untrue, but that this is the state of things. It&amp;#x27;s that cloud providers are now often seen as the only responsible way to operate infrastructure, and in the process we hand over so much control of our tooling. We let ourselves be convinced that simplicity was worth a 10x premium, and admitted we were not grown up enough to handle the tools we had made for ourselves.&lt;p&gt;Sure, I know it is more complex than that. But I also feel sad about it.</text></item></parent_chain><comment><author>zer00eyz</author><text>&amp;gt;&amp;gt;&amp;gt; It&amp;#x27;s that cloud providers are now often seen as the only responsible way to operate infrastructure&lt;p&gt;23 billion.&lt;p&gt;Thats the profit for AWS in 2023.&lt;p&gt;23 billon that AWS users pissed away.&lt;p&gt;AWS is NOT cheap. I have quite a few clients who, could save lots of money dumping their cloud provider and setting up their own racks, hiring SA&amp;#x27;s. I have others who, if they optimized any of their stack could cut their AWS bills by half.&lt;p&gt;Having survived the 2000 bubble the lessons are going to have to be re-learned. Everything has cost and value and managing that is going to become an engineering task in the near future.</text></comment>
<story><title>Implementing system-versioned tables in Postgres</title><url>https://hypirion.com/musings/implementing-system-versioned-tables-in-postgres</url></story><parent_chain><item><author>adamcharnock</author><text>&amp;gt; Now, there are extensions out there that implement versioning – temporal_tables being the most popular I think – but none are supported for managed Postgres instances on e.g. Azure or AWS. This means that if we want system-versioned tables, we’re forced to make it ourselves.&lt;p&gt;This really provokes a wild geek rage inside me. Not that it is untrue, but that this is the state of things. It&amp;#x27;s that cloud providers are now often seen as the only responsible way to operate infrastructure, and in the process we hand over so much control of our tooling. We let ourselves be convinced that simplicity was worth a 10x premium, and admitted we were not grown up enough to handle the tools we had made for ourselves.&lt;p&gt;Sure, I know it is more complex than that. But I also feel sad about it.</text></item></parent_chain><comment><author>refset</author><text>It&amp;#x27;s especially tragic knowing that Postgres did originally have system-time-like versioning built-in. Instead we get to enjoy being upsold on proprietary ETL-to-Redshift, AlloyDB, etc.</text></comment>