Просмотр новости
Найдите то, что Вас интересует
Спутники
РН
SpaceX
Роскосмос
NASA
СпутникиРНSpaceXРоскосмосNASA
The PostgreSQL Global Development Group announces that the second beta release of
PostgreSQL 19 is now available for download.
This release contains PostgreSQL 19 feature previews ahead of general
availability, though some details of the release can change during the beta
period.
You can find information about all of the PostgreSQL 19 features and changes in
the release notes:
https://www.postgresql.org/docs/19/release-19.html
In the spirit of the open source PostgreSQL community, we strongly encourage you
to test the new features of PostgreSQL 19 on your systems to help us eliminate
bugs and other issues. While we do not advise you to run beta versions in
production environments, we encourage you to find ways to run your typical
application workloads against this beta release.
Your testing and feedback help the community ensure that PostgreSQL 19
upholds our standards of delivering a stable, reliable release of the
world's most advanced open source relational database. Please read more about
our beta testing process and how
you can contribute:
https://www.postgresql.org/developer/beta/
Upgrading to PostgreSQL 19 Beta 2
To upgrade to PostgreSQL 19 Beta 2 from an earlier version of PostgreSQL,
you will need to use a strategy similar to upgrading between major versions of
PostgreSQL (e.g. pg_upgrade or pg_dump / pg_restore). For more
information, please visit the documentation section on
upgrading.
Changes Since Beta 1
Fixes and changes in PostgreSQL 19 Beta 2 include:
Fix a regression in vacuumdb --analyze-in-stages for partitioned tables.
Fix servicefile to show correct file after fallback to system file.
Fix tuple deformation optimization for virtual generated columns.
Allow pg_createsubscriber to accept duplicate publication names.
Fix REPACK worker not being cleaned up on a FATAL exit.
Several fixes for the new FOR PORTION OF temporal table syntax.
Fix race condition when logical decoding activation is concurrently
interrupted.
Disallow negative values for max_retention_duration.
Fix md5_password_warnings for role and database settings.
Several fixes for the new SQL/PGQ property graph feature.
Fix autovacuum's multixact-age score calculation, which could become infinite.
Revert non-text output formats for pg_dumpall.
Fix locking for ALTER DOMAIN ... VALIDATE CONSTRAINT.
Fix how postgres_fdw handles imported foreign-table statistics.
Please see the release notes
for a complete list of new and changed features:
https://www.postgresql.org/docs/19/release-19.html
Testing for Bugs & Compatibility
The stability of each PostgreSQL release greatly depends on you, the community,
to test the upcoming version with your workloads and testing tools to find bugs
and regressions before the general availability of PostgreSQL 19. As this is a
Beta, minor 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:
https://www.postgresql.org/account/submitbug/
Beta Schedule
This is the second beta release of version 19. The PostgreSQL Project will
release additional betas as required for testing, followed by one or more
release candidates, until the final release around September/October 2026. For further
information please see the Beta Testing
page.
Links
Download
Beta Testing Information
PostgreSQL 19 Beta Release Notes
PostgreSQL 19 Open Issues
Submit a Bug
Donate
Posted on 2026-07-16 by PostgreSQL Global Development Group
PostgreSQL Project
The PostgreSQL Global Development Group announces that the second beta release of PostgreSQL 19 is now available for download. This release contains PostgreSQL 19 feature previews ahead of general availability, though some details of the release can change during the beta period.
You can find information about all of the PostgreSQL 19 features and changes in the release notes:
https://www.postgresql.org/docs/19/release-19.html
In the spirit of the open source PostgreSQL community, we strongly encourage you to test the new features of PostgreSQL 19 on your systems to help us eliminate bugs and other issues. While we do not advise you to run beta versions in production environments, we encourage you to find ways to run your typical application workloads against this beta release.
Your testing and feedback help the community ensure that PostgreSQL 19 upholds our standards of delivering a stable, reliable release of the world's most advanced open source relational database. Please read more about our beta testing process and how you can contribute:
https://www.postgresql.org/developer/beta/
Upgrading to PostgreSQL 19 Beta 2To upgrade to PostgreSQL 19 Beta 2 from an earlier version of PostgreSQL,
you will need to use a strategy similar to upgrading between major versions of
PostgreSQL (e.g. pg_upgrade or pg_dump / pg_restore). For more
information, please visit the documentation section on
upgrading.
Fixes and changes in PostgreSQL 19 Beta 2 include:
vacuumdb --analyze-in-stages for partitioned tables.servicefile to show correct file after fallback to system file.pg_createsubscriber to accept duplicate publication names.REPACK worker not being cleaned up on a FATAL exit.FOR PORTION OF temporal table syntax.max_retention_duration.md5_password_warnings for role and database settings.pg_dumpall.ALTER DOMAIN ... VALIDATE CONSTRAINT.postgres_fdw handles imported foreign-table statistics.Please see the release notes for a complete list of new and changed features:
https://www.postgresql.org/docs/19/release-19.html
Testing for Bugs & CompatibilityThe stability of each PostgreSQL release greatly depends on you, the community, to test the upcoming version with your workloads and testing tools to find bugs and regressions before the general availability of PostgreSQL 19. As this is a Beta, minor 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:
https://www.postgresql.org/account/submitbug/
Beta ScheduleThis is the second beta release of version 19. The PostgreSQL Project will release additional betas as required for testing, followed by one or more release candidates, until the final release around September/October 2026. For further information please see the Beta Testing page.
Links| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | powa-archivist 5.2.0 is out! | 0 | 5 | 12-07-2026 |
| 2 | Odyssey 1.5.1 released | 5 | 7 | 14-07-2026 |
| 3 | Postgres Professional усилила Postgres Pro Standard 18.4.1 встроенной отказоустойчивостью BiHA | 0 | 5 | 18-06-2026 |
| 4 | СУБД PostgreSQL обновилась до версии 18 | 0 | 10 | 06-10-2025 |
| 5 | Postgres Professional выпустила ProGate 1.3.0 с поддержкой Shardman и отказоустойчивой репликацией | 0 | 5 | 08-07-2026 |
| 6 | patera-database 0.9.0 | 0 | 0 | 10-07-2026 |
| 7 | openSUSE pacemaker Important Denial Of Service CVE-2026-10649 2026-21196-1 | 0 | 5 | 03-07-2026 |
| 8 | openSUSE GStreamer-Plugins-Bad Important Out-of-Bounds DoS CVE-2026-52719 | 0 | 5 | 03-07-2026 |
| 9 | 9 Best Free and Open Source Configuration Management Databases | 0 | 5 | 15-07-2026 |
| 10 | move - Mort release without updated move plugin gives issue during move actions. see PR #319 | -2 | 5 | 15-07-2026 |