The PostgreSQL Global Development Group announces that the second beta release of PostgreSQL 13 is now available for download. This release contains previews of all features that will be available in the final release of PostgreSQL 13, though some details of the release could change before then.
You can find information about all of the features and changes found in PostgreSQL 13 in the release notes:
In the spirit of the open source PostgreSQL community, we strongly encourage you to test the new features of PostgreSQL 13 in your systems to help us eliminate any bugs or other issues that may exist. While we do not advise you to run PostgreSQL 13 Beta 2 in your production environments, we encourage you to find ways to run your typical application workloads against this beta release.
You can read more about our beta testing process and how you can contribute here:
To upgrade to PostgreSQL 13 Beta 2 from Beta 1 or an earlier version of
PostgreSQL, you will need to use a strategy similar to upgrading between
major versions of PostgreSQL (e.g.
For more information, please visit the documentation section on
There have been many bug fixes for PostgreSQL 13 reported during the Beta 1 period and applied to the Beta 2 release. This includes:
effective_io_concurrencyconfiguration parameter is now simpler to use. To convert from the old value to the new value, you can use this formula:
SELECT round(sum(OLD / n::float)) from generate_series(1, OLD) s(n);.
enable_hashagg_diskconfiguration parameter is renamed to
hashagg_avoid_disk_planand defaults to
enable_groupingsets_hash_diskconfiguration parameter has been removed.
EXPLAIN ANALYZEoutput for parallel query plans that have hash aggregates spill to disk now show max memory and disk usage per worker.
Please see the release notes for a complete list of new and changed features:
The stability of each PostgreSQL release greatly depends on you, the community, to test the upcoming version with your workloads and testing tools in order to find bugs and regressions before the general availability of PostgreSQL 13. As this is a Beta, changes to database behaviors, feature details, and APIs are still possible. Your feedback and testing will help determine the final tweaks on the new features, so please test in the near future. The quality of user testing helps determine when we can make a final release.
A list of open issues is publicly available in the PostgreSQL wiki. You can report bugs using this form on the PostgreSQL website:
This is the second beta release of version 13. The PostgreSQL Project will release additional betas as required for testing, followed by one or more release candidates, until the final release in late 2020. For further information please see the Beta Testing page.