This blog is about my work on the Postgres open source database, and is published on Planet PostgreSQL. PgLife allows monitoring of all Postgres community activity.
Online status:
Unread Postgres emails:
Email graphs:
incoming,
outgoing,
unread,
commits
(details)
Geopolitical Postgres
Wednesday, April 9, 2025
Postgres is a data storage tool, and as a tool it is neutral in how it is used. Tools can be used for good, for harm, and because Postgres is open source, the community doesn't even know how it is used.
My first knowledge of non-traditional uses of Postgres was in 2003 during a Postgres training. During a break, someone whispered to me that one of the attendees was from a pornographic video company, and that Postgres was very popular in that industry. The more I thought about it, the more it made sense — many database companies didn't want to do business with them, but Postgres was open source so they could use it easily.
The flexibility of Postgres to be used without restrictions didn't become apparent to me again until 2014, when Russia invaded Crimea and fermented a war in Ukraine's Donbas region. Russia was internationally sanctioned, and many technology companies stopped doing business in Russia, causing Russian companies to scramble for alternatives. In reaction Russia implemented a nation-wide effort called "import substitution" to replace imported goods and products with locally produced ones. A logical database alternative was Postgres, for the same reason it was a popular option for pornographic video companies.
Adoption of Postgres in Russia skyrocketed. Existing Russian Postgres companies were suddenly in great demand, and new companies were formed. The invasion of Ukraine in 2022 greatly increased Russian sanctions. Today, though Russian Postgres community members struggle to attend in-person conferences, there has been little impact on their community involvement.
The sanctions on Russia have triggered other countries to consider information technology self-sufficiency. Enterprises in these countries were already switching to Postgres, but the wish to have a data storage tool that that is independent of international sanctions has brought government pressure on these enterprises to speed up their migrations. China, with its often-threatened invasion of Taiwan, is particularly keen to achieve self-sufficiency. The recent implementation of U.S. tariffs further cemented the value of software self-sufficiency.
Using Postgres in frowned-up industries or to minimize international sanctions or tariffs are probably not the goals that the designers of open source intended, but they did have the concept of unrestricted use. No one can restrict your use of open source, which is a good thing — no one wants someone else deciding if their software usage is acceptable.
Saturday, February 22, 2025
I first blogged about Transparent Data Encryption (tde) in 2019, which was more thoroughly analyzed in a blog post in 2023. An email exchange in December 2024 summarized the most up-to-date status of this feature:
That analysis was not challenged in the email thread, which makes me conclude that a Postgres core implementation of tde is unlikely in the near future. An interesting email thread reply was more philosophical:
This argues that a Postgres core implementation of tde is inevitable since there are few cases where multiple commercial feature implementations have not been eventually implemented in core. A counter argument is that tde might not fit that pattern since its value is mostly regulatory and ease-of-deployment. Time will tell.
Post a CommentTuesday, January 28, 2025
I delivered my presentation Databases in the AI Trenches today as part of a tutorial at Prague PostgreSQL Developer Day, so I have placed my slides online. It focuses on semantic search, generative AI, and rag, and builds on my discriminative AI talk, Postgres and the Artificial Intelligence Landscape. I will also be giving this talk on Saturday and the Tuesday after that.