Experiments
Stop when this page is not the decision
A published page can record a stop. It does not, by itself, record the next plan.
postgresql.org published this account (2026-09-24): PostgreSQL announced 19 Beta 4 on September 24, 2026 and listed reverts of SQL/PGQ, online checksum toggle, temporal FOR PORTION OF, MERGE/SPLIT PARTITIONS, and several DDL helper functions, plus REPACK/WAIT FOR/replication fixes.
This guide uses that public page as the example. This site did not run the test, close the deal, or measure the product.
Write only what the page says
The page's claim is: PostgreSQL announced 19 Beta 4 on September 24, 2026 and listed reverts of SQL/PGQ, online checksum toggle, temporal FOR PORTION OF, MERGE/SPLIT PARTITIONS, and several DDL helper functions, plus REPACK/WAIT FOR/replication fixes.
Put the URL under that sentence. If a later recap adds a number or a date, keep the original page as the record.
A published page can record a stop. It does not, by itself, record the next plan.
Do the site's check on this one page. Fill a line only when the page supports it. Where the page is silent, write Not stated.
A finished note names the page, the date, and the limit of the claim. It does not borrow a result from a different story.
Stop at the untested line
Anything you did not open, install, or count stays untested. Leave that line visible.
Source page: PostgreSQL 19 Beta 4 released with multiple planned-feature reverts.
Sources: PostgreSQL 19 Beta 4 released with multiple planned-feature reverts