Greenplum 7 beta.2 released!!!

16 views
Skip to first unread message

Ashwin Agrawal

unread,
Mar 20, 2023, 2:28:22 PM3/20/23
to Greenplum Developers, Greenplum Users
The Greenplum Team announces the Beta.2 release of Greenplum
Database 7 is now available for [download]
(https://github.com/greenplum-db/gpdb/releases/tag/7.0.0-beta.2).

Please continue to play with it and provide your feedback to further
improve GPDB7.

Team continues to put in hard work to take GPDB7 forward with features
and fixes. Around 260 commits were made on top of 7.0.0-beta.1 for
7.0.0-beta.2.

Greenplum 7 Beta.2 High-lights (not full list):

- Greenplum Database now includes the catalog views pg_stat_wal which
  displays WAL information and pg_stat_slru to track simple
  least-recently-used (SLRU) caches, along with the configuration
  parameter track_wal_io_timing which provides details of the I/O
  impact of WAL writes.

- Support pg_stat_progress_cluster view for append-optimized tables.

- VACUUM can now run only against all auxiliary tables of an
  append-optimized table with the option AO_AUX_ONLY, skipping base AO
  table.

- The Greenplum PL/R language extension is now included, at version
  3.1.0.  Greenplum Database optimizes the use of snapshots when using
  immutable functions. It avoids taking a distributed snapshot and
  uses the local snapshot, resulting in improved performance for OLTP.

- Order-agnostic aggregates can now be designated as safe for
  execution on replicated slices by specifying the REPSAFE = true
  parameter to the CREATE AGGREGATE command.

- Greenplum Database 7 introduces the gp_autovacuum_scope server
  configuration parameter. You can use this parameter to define the
  tables (catalog, auxiliary) that Greenplum Database automatically
  vacuums when autovacuum=on (the default).

- The wal_keep_segments server configuration parameter has been
  replaced by the wal_keep_size parameter.

- Add filenum field to pg_attribute_encoding to help future
  optimizations for CO tables for column type changes and drop
  columns.

- Implement pg_backend_memory_contexts and
  gp_log_backend_memory_contexts system views.

- Add support for foreign partitions in Orca.

- Skip full table rewrite for ADD COLUMN for AOCO table with NULL
  default. Previously, only with non default value the optimization
  existed.

- Report VACUUM progress for append-optimized tables.

- Introduce the "version" attribute to pg_appendonly. Remove visimapidxid
  and blkdiridxid fields from pg_appendonly to reduce its size. Also,
  adds relcacahe to speed up meta-data lookups.

- Support HashIndexes in Orca.

- Add support for more progress reporting in COPY.

- Report progress of streaming base backup.

- Report progress of ANALYZE commands.

- Resource Groups now by default bypass query with only catalog
  tables.

- Support Direct Dispatch for a randomly distributed table, when
  filtered on gp_segment_id.

- AOCO table performance enhancements to use column projection for
  partition constraint validation on ADD/CREATE PARTITION OF and
  ATTACH/EXCHANGE.

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).



--
Ashwin Agrawal (VMware)
Reply all
Reply to author
Forward
0 new messages