<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:fh="http://purl.org/syndication/history/1.0"><channel><title>CommitFest | CommitFest Blog</title><description>An independent guide to PostgreSQL CommitFest updates, patch review, and participation.</description><link>https://commitfest.com/</link><language>en</language><fh:complete/><atom:link rel="self" href="https://commitfest.com/blog/rss.xml"/><item><title>PostgreSQL 19’s revised release plan: what changed</title><link>https://commitfest.com/blog/postgresql-19-revised-release-plan/</link><guid isPermaLink="true">https://commitfest.com/blog/postgresql-19-revised-release-plan/</guid><description>PostgreSQL 19 is planned for November 19, subject to testing. Here’s the revised sequence and why the release team wants another candidate first.</description><pubDate>Thu, 29 Oct 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;PostgreSQL 19 is now planned for &lt;strong&gt;November 19, 2026&lt;/strong&gt;, rather than the earlier October 29 target. That is a plan, not a guarantee: further issues could require another release candidate or delay. &lt;a href=&quot;https://www.postgresql.org/about/news/postgresql-19-rc-1-released-3409/&quot;&gt;RC1 announcement&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The release team’s explanation is concrete. A substantial set of fixes is due in the supported-version update on November 12. The team wants those fixes included in PostgreSQL 19 RC2, scheduled for the same day, before proceeding to general availability. &lt;a href=&quot;https://www.postgresql.org/message-id/f161fbb7-e193-42eb-bec7-4cfc1af74a50@postgresql.org&quot;&gt;Schedule update&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The revised sequence:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;October 15:&lt;/strong&gt; RC1 released.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;November 12:&lt;/strong&gt; RC2 planned alongside supported-version updates.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;November 19:&lt;/strong&gt; general availability planned, subject to testing.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The September 28 announcement had targeted October 29, also conditionally. This is a three-week change to that target—not evidence of a fixed November release schedule. &lt;a href=&quot;https://www.postgresql.org/message-id/915517c4-d0ee-49f9-bbeb-c683ef2b9d3f%40postgresql.org&quot;&gt;Earlier announcement&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;For developers, the useful next step is testing. Try representative workloads and check dependent tools against the release candidate in a separate test environment. PostgreSQL says beta and release-candidate builds are not intended for production. &lt;a href=&quot;https://www.postgresql.org/developer/beta/&quot;&gt;Testing guidance&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;A planned date is not a shipped release. A release candidate is a chance to find problems before it becomes one.&lt;/p&gt;
</content:encoded></item></channel></rss>