<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pg_alastair on Percona Community</title><link>https://percona.community/tags/pg_alastair/</link><description>Recent content in Pg_alastair 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>Thu, 26 Feb 2026 14:00:00 +0000</lastBuildDate><atom:link href="https://percona.community/tags/pg_alastair/index.xml" rel="self" type="application/rss+xml"/><item><title>A reponsible role for AI in Open Source projects?</title><link>https://percona.community/blog/2026/02/26/responsible-ai-for-oss/</link><pubDate>Thu, 26 Feb 2026 14:00:00 +0000</pubDate><guid>https://percona.community/blog/2026/02/26/responsible-ai-for-oss/</guid><description>&lt;p>AI-driven pressure on open source maintainers, reviewers and, even, contributors, has been very much in the news lately. Nobody needs another set of edited highlights on the theme from me. For a Postgres-specific view, and insight on how low quality AI outputs affect contributors, &lt;a href="https://vondra.me/posts/the-ai-inversion/" target="_blank" rel="noopener noreferrer">Tomas Vondra published a great post on his blog recently&lt;/a>, which referenced &lt;a href="https://www.pgevents.ca/events/pgconfdev2025/schedule/session/254-committer-review-an-exercise-in-paranoia/" target="_blank" rel="noopener noreferrer">an interesting talk by Robert Haas&lt;/a> at PGConf.dev in Montreal last year. I won’t rehash the content here, they’re both quite quick reads and well worth the time.&lt;/p></description></item><item><title>PostgreSQL coffee break: version upgrade related reindexing - reasons</title><link>https://percona.community/blog/2026/02/25/postgresql-coffee-break-version-upgrade-related-reindexing-reasons/</link><pubDate>Wed, 25 Feb 2026 11:00:00 +0000</pubDate><guid>https://percona.community/blog/2026/02/25/postgresql-coffee-break-version-upgrade-related-reindexing-reasons/</guid><description>&lt;p>During FOSDEM I had a chance to join a &lt;a href="https://fosdem.org/2026/schedule/event/ZF8ZLX-zero-downtime-postgresql-upgrades/" target="_blank" rel="noopener noreferrer">presentation&lt;/a> by &lt;a href="https://www.linkedin.com/in/alexander-sosna-7193688b/" target="_blank" rel="noopener noreferrer">Alexander Sosna&lt;/a> of GitLab on the backup procedure he has followed with his team to decrease the downtime during major upgrades. I highly recommend the talk, definitely worth watching!&lt;/p>
&lt;p>I loved the presentation, especially since a similar procedure is what we recommend our users as well. Unfortunately it’s not for everyone: it’s applicable ONLY when you can stop DDL operations on your database cluster for some time. As you can imagine that’s not a case for every deployment.&lt;/p></description></item><item><title>A thread through my 2025 Postgres events</title><link>https://percona.community/blog/2025/11/10/thread-through-2025-pgconfs/</link><pubDate>Mon, 10 Nov 2025 07:00:00 +0000</pubDate><guid>https://percona.community/blog/2025/11/10/thread-through-2025-pgconfs/</guid><description>&lt;p>I recently got back from PostgreSQL Conference Europe in Riga, marking the end of my conference activities for 2025. The speakers were great. The audience, for the Extensions Showcase on Community Day on Tuesday and my Kubernetes from the database out talk, were great. The event team was great. The singing at karaoke was terrible, but it’s supposed to be.&lt;/p>
&lt;p>After attending a good few events this year, starting with CERN PGDay in mid-January, I wanted to write something about more than just the most recent event. I see a common thread across presentations and sessions at a number of events over the year, that is, scale-out Postgres and particularly, its use in non-profit scientific environments.&lt;/p></description></item></channel></rss>