Greenplum 7 beta.5 released!!!
53 views
Skip to first unread message
Ashwin Agrawal
Aug 7, 2023, 1:42:01 PM8/7/23
to Greenplum Developers, Greenplum Users
The Greenplum Team announces that the Beta.5 release of Greenplum
Database 7 is now available for [download]
(https://github.com/greenplum-db/gpdb/releases/tag/7.0.0-beta.5).
We are getting really close to GA ready. Please continue to play with
GPDB7 and provide your feedback to further improve GPDB7.
Team continues to do amazing work to take GPDB7 forward with features
and fixes. Around 239 commits were made on top of 7.0.0-beta.4 for
7.0.0-beta.5. Most of the focus now is on stability and fixing
outstanding issues.
Greenplum 7 Beta.5 Highlights:
=======================
- gppkg now includes the new subcommands migrate and sync, as well as
the global option --cluster-info that allows you to install or
upgrade packages when Greenplum Database is not running.
- gp_read_error_log() is enhanced to detect division by zero, JSON
mapping, and unsupported unicode errors encountered during foreign
scans of external tables. This feature is not supported when the
Greenplum Query Optimizer (GPORCA) is enabled.
- The CREATE TABLE ... (LIKE ... INCLUDING <keyword> ) command now
supports AM, ENCODING, and RELOPT keywords to copy the access
method, column encoding, and/or relation options from the
source/original table.
- The postgres_fdw module includes support for accessing data managed
by multiple remote PostgreSQL servers from a single foreign table.
- You may now configure device I/O usage at the resource group level
via the new IO_LIMIT resource group attribute. Specifically, you can
control for processes in a resource group:
- the maximum bandwidth of read/write operations from the disk per second
- the maximum number of IO read/write operations from the disk per second
You may control this for particular tablespaces or across all tablespaces.
- The diskquota module was updated to version 2.2.2, which includes
these changes:
- Support for upgrading from all versions. Previous diskquota
releases supported upgrading only between versions 1.x and 2.0
and between minor 2.x versions.
- Reduces the number of [diskquota] disk quota worker process is
monitoring database:<name> log messages to one per hour when
operating in dynamic mode.
- [ORCA] Implement dynamic index only scan
- gprecoverseg: Add ability to handle interrupts
- brin ao/co: Mark dead ranges as empty on VACUUM
- Replace pygresql with psycopg2 for gpMgmt tools
- Set postmaster status ready after walreceiver up
- minirepro: collect using sequence
- Update relstats after index builds on the QD
- brin: Adjust the default value of pages_per_range
- gpcheckcat: Add new option -x to set session level GUCs
- Replace pygresql with psycopg2 for gpload
- Add gp_stat_progress_dtx_recovery for observability
- Delete gpmapreduce code
- Import collations at gpinitsystem time
- Make sure database-wide VACUUM FREEZE don't leave unfrozen rows in pg_stat_last_operation/pg_stat_last_shoperation
- Introducing optional hostname parameter in the gprecoverseg input config file
- Update behavior of size calculation for AO tables
- Add covering index tests for Append-Optimized table
- [ORCA] Enable Index-Only Scan on CTE
Beta Information
=============
Greenplum Beta releases are pre-release testing versions before a new
release is generally available. We release these to the public for
testing before our final release. Greenplum Betas are not meant for
use in production systems. Beta releases are especially helpful for
developers of platforms, drivers, tools, and utilities that depend
upon Greenplum Database in order to prepare for changes in the new
version.
We strongly advise against using Beta versions of Greenplum Database
in production installations or active development projects. While the
Greenplum Database code is continuously subject to several automated
and manual tests, Beta releases might have serious bugs. Features are
subject to changes that are backward incompatible at any time during
the development of the Betas and could possibly be removed altogether.
Testing for Bugs & Compatibility
=========================
The stability of each Greenplum Database 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 general
availability. As this is a Beta, changes to database behaviors,
feature details, and APIs are possible. Your feedback and testing will
help determine the final adjustments to the new features, so please
test. The quality of user testing helps determine when we can make a
final release.
You can report bugs using [github
issues](https://github.com/greenplum-db/gpdb/issues).
Links
====
- [7.0.0-beta.5 Release](https://github.com/greenplum-db/gpdb/releases/tag/7.0.0-beta.5)
- [Greenplum Version 7 Youtube Playlist](https://www.youtube.com/playlist?list=PL4duir3J-8GX9EmTGRXoBE9vTKFWHsXLC)
- [ALTER TABLE In Greenplum 7: Avoiding Table Rewrite](https://greenplum.org/alter-table-in-gpdb-7-avoiding-table-rewrite)
Database 7 is now available for [download]
(https://github.com/greenplum-db/gpdb/releases/tag/7.0.0-beta.5).
We are getting really close to GA ready. Please continue to play with
GPDB7 and provide your feedback to further improve GPDB7.
Team continues to do amazing work to take GPDB7 forward with features
and fixes. Around 239 commits were made on top of 7.0.0-beta.4 for
7.0.0-beta.5. Most of the focus now is on stability and fixing
outstanding issues.
Greenplum 7 Beta.5 Highlights:
=======================
- gppkg now includes the new subcommands migrate and sync, as well as
the global option --cluster-info that allows you to install or
upgrade packages when Greenplum Database is not running.
- gp_read_error_log() is enhanced to detect division by zero, JSON
mapping, and unsupported unicode errors encountered during foreign
scans of external tables. This feature is not supported when the
Greenplum Query Optimizer (GPORCA) is enabled.
- The CREATE TABLE ... (LIKE ... INCLUDING <keyword> ) command now
supports AM, ENCODING, and RELOPT keywords to copy the access
method, column encoding, and/or relation options from the
source/original table.
- The postgres_fdw module includes support for accessing data managed
by multiple remote PostgreSQL servers from a single foreign table.
- You may now configure device I/O usage at the resource group level
via the new IO_LIMIT resource group attribute. Specifically, you can
control for processes in a resource group:
- the maximum bandwidth of read/write operations from the disk per second
- the maximum number of IO read/write operations from the disk per second
You may control this for particular tablespaces or across all tablespaces.
- The diskquota module was updated to version 2.2.2, which includes
these changes:
- Support for upgrading from all versions. Previous diskquota
releases supported upgrading only between versions 1.x and 2.0
and between minor 2.x versions.
- Reduces the number of [diskquota] disk quota worker process is
monitoring database:<name> log messages to one per hour when
operating in dynamic mode.
- [ORCA] Implement dynamic index only scan
- gprecoverseg: Add ability to handle interrupts
- brin ao/co: Mark dead ranges as empty on VACUUM
- Replace pygresql with psycopg2 for gpMgmt tools
- Set postmaster status ready after walreceiver up
- minirepro: collect using sequence
- Update relstats after index builds on the QD
- brin: Adjust the default value of pages_per_range
- gpcheckcat: Add new option -x to set session level GUCs
- Replace pygresql with psycopg2 for gpload
- Add gp_stat_progress_dtx_recovery for observability
- Delete gpmapreduce code
- Import collations at gpinitsystem time
- Make sure database-wide VACUUM FREEZE don't leave unfrozen rows in pg_stat_last_operation/pg_stat_last_shoperation
- Introducing optional hostname parameter in the gprecoverseg input config file
- Update behavior of size calculation for AO tables
- Add covering index tests for Append-Optimized table
- [ORCA] Enable Index-Only Scan on CTE
Beta Information
=============
Greenplum Beta releases are pre-release testing versions before a new
release is generally available. We release these to the public for
testing before our final release. Greenplum Betas are not meant for
use in production systems. Beta releases are especially helpful for
developers of platforms, drivers, tools, and utilities that depend
upon Greenplum Database in order to prepare for changes in the new
version.
We strongly advise against using Beta versions of Greenplum Database
in production installations or active development projects. While the
Greenplum Database code is continuously subject to several automated
and manual tests, Beta releases might have serious bugs. Features are
subject to changes that are backward incompatible at any time during
the development of the Betas and could possibly be removed altogether.
Testing for Bugs & Compatibility
=========================
The stability of each Greenplum Database 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 general
availability. As this is a Beta, changes to database behaviors,
feature details, and APIs are possible. Your feedback and testing will
help determine the final adjustments to the new features, so please
test. The quality of user testing helps determine when we can make a
final release.
You can report bugs using [github
issues](https://github.com/greenplum-db/gpdb/issues).
Links
====
- [7.0.0-beta.5 Release](https://github.com/greenplum-db/gpdb/releases/tag/7.0.0-beta.5)
- [Greenplum Version 7 Youtube Playlist](https://www.youtube.com/playlist?list=PL4duir3J-8GX9EmTGRXoBE9vTKFWHsXLC)
- [ALTER TABLE In Greenplum 7: Avoiding Table Rewrite](https://greenplum.org/alter-table-in-gpdb-7-avoiding-table-rewrite)
Reply all
Reply to author
Forward
0 new messages