<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pg_kwagner on Percona Community</title><link>https://percona.community/tags/pg_kwagner/</link><description>Recent content in Pg_kwagner on Percona Community</description><generator>Hugo</generator><language>en-us</language><copyright>© Percona Community. MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.</copyright><lastBuildDate>Wed, 13 May 2026 10:00:00 +0000</lastBuildDate><atom:link href="https://percona.community/tags/pg_kwagner/index.xml" rel="self" type="application/rss+xml"/><item><title>Two projects, one mission - hackorum and pginbox join forces</title><link>https://percona.community/blog/2026/05/13/two-projects-one-mission-hackorum-and-pginbox-join-forces/</link><pubDate>Wed, 13 May 2026 10:00:00 +0000</pubDate><guid>https://percona.community/blog/2026/05/13/two-projects-one-mission-hackorum-and-pginbox-join-forces/</guid><description>&lt;p>Last week, Zsolt and I jumped on a call with someone who had been building something remarkably similar to what we had been working on, completely independently. That someone is Jack Bonatakis, the creator of &lt;a href="https://pginbox.dev/" target="_blank" rel="noopener noreferrer">pginbox.dev&lt;/a>, and that call turned into one of the most energizing conversations we&amp;rsquo;ve had since launching &lt;a href="https://hackorum.dev/" target="_blank" rel="noopener noreferrer">hackorum.dev&lt;/a>.&lt;/p>
&lt;h3 id="two-builders-one-problem">&lt;strong>Two builders, one problem&lt;/strong>&lt;/h3>
&lt;p>When we launched Hackorum back in January, the goal was simple but important: make the pg-hackers mailing list actually readable. The list is the heartbeat of PostgreSQL core development, patches are proposed, debated, iterated on, and committed entirely through it. But the interface? Decades-old email threads. Dense, fast-moving, and not exactly welcoming to newcomers or even experienced contributors trying to manage the volume.&lt;/p></description></item><item><title>PGDay and FOSDEM Report from Kai</title><link>https://percona.community/blog/2026/02/04/pgday-and-fosdem-report-from-kai/</link><pubDate>Wed, 04 Feb 2026 10:00:00 +0000</pubDate><guid>https://percona.community/blog/2026/02/04/pgday-and-fosdem-report-from-kai/</guid><description>&lt;p>The following thoughts and comments are completely my personal opinion and do not reflect my employers thoughts or beliefs. If you don&amp;rsquo;t like anything in this post, reach out to me directly, so I can ignore it ;-).&lt;/p>
&lt;p>I&amp;rsquo;m currently on the train on my way back home from FOSDEM this year and man, I&amp;rsquo;m exhausted but also happy. Why? Because the PG and FOSDEM community is just crazily awesome. While it&amp;rsquo;s always too much of everything, it&amp;rsquo;s at the same time inspiring to see so many enthusiastic IT nerds in one place, discussing and working on what they love - technology and engineering challenges.&lt;/p></description></item><item><title>Hackorum - A Forum-Style View of pg-hackers</title><link>https://percona.community/blog/2026/02/02/hackorum-a-forum-style-view-of-pg-hackers/</link><pubDate>Mon, 02 Feb 2026 00:00:00 +0000</pubDate><guid>https://percona.community/blog/2026/02/02/hackorum-a-forum-style-view-of-pg-hackers/</guid><description>&lt;p>Last year at pgconf.dev, there was a discussion about improving the user interface for the PostgreSQL hackers mailing list, which is the main communication channel for PostgreSQL core development. Based on that discussion, I want to share a small project we have been working on:&lt;/p>
&lt;p>&lt;a href="https://hackorum.dev/" target="_blank" rel="noopener noreferrer">https://hackorum.dev/&lt;/a>&lt;/p>
&lt;p>Hackorum provides a &lt;strong>read-only (for now)&lt;/strong> web view of the mailing list with a more forum-like presentation. It is a &lt;strong>work-in-progress proof of concept&lt;/strong>, and we are primarily looking for feedback on whether this approach is useful and what we should improve next.&lt;/p></description></item><item><title>PGScorecard - PostgreSQL Compatibility Index</title><link>https://percona.community/blog/2025/11/13/pgscorecard-postgresql-compatibility-index/</link><pubDate>Thu, 13 Nov 2025 00:00:00 +0000</pubDate><guid>https://percona.community/blog/2025/11/13/pgscorecard-postgresql-compatibility-index/</guid><description>&lt;p>We’re excited to share that our recent test run using the &lt;a href="https://github.com/secp256k1-sha256/postgres-compatibility-index/blob/main/readme.md" target="_blank" rel="noopener noreferrer">Postgres Compatibility Index (PCI)&lt;/a> achieved 100% compatibility.&lt;/p>
&lt;p>The PCI was created to bring clarity to the often used but loosely defined term &amp;ldquo;PostgreSQL compatible.&amp;rdquo; As Mayur explains in his article &lt;a href="https://drunkdba.medium.com/the-making-of-postgres-is-5034c0dc4639" target="_blank" rel="noopener noreferrer">The Making of &amp;lsquo;Postgres Is&amp;rsquo;&lt;/a>, the goal is simple: to ensure that when a system claims to be compatible with PostgreSQL, it truly behaves like upstream PostgreSQL in practice. The PCI accomplishes this by running a comprehensive set of tests across features like data types, procedural functions, constraints, extensions, and more, and producing a measurable, transparent score. This gives users and vendors a reliable benchmark rather than relying on marketing claims.&lt;/p></description></item></channel></rss>