ADB releases
6.22.1
Date: 15.02.2023
Upgraded pgbouncer to 1.18 |
Upgraded gpbackup to 1.27 |
Upgraded plcontainer to 2.2 |
Implemented a buffer parameter in the gpcheckperf utility |
ADB bundle: added a checkbox to echo ADB-specific metrics to Monitoring Clients |
Implemented ADBM 1.1.0 |
Implemented ADBCC 4.1.0 |
ADB bundle: removed the gppefmon dependency from ADBCC and refactored the ADBCC configs |
ADB bundle: renamed |
Added a precaution annotation to /home/gpadmin/arenadata_configs/postgresql.conf |
Made migration of the |
Components in ADB did not change their state to |
High memory utilization for queries with SQL subqueries |
The service query collect_table_stats.sql periodically hung |
The PXF encryption error: |
It was impossible to add the Chrony Secondary component on a new Standby host |
PXF did not start with enabled option encryption: |
Refactored arenadata_segments_monitor.sh to avoid crontab for a Standby node |
|
The invalid byte sequence for encoding UTF8 in logs during accessing |
GPORCA produced a bogus plan for queries with CTE during handling distribution for Sequence children |
The |
Incorrect |
The issue with changing an ADBCC service configuration file via ADCM |
Fixed a system database name for ADBM |
Fixed known issues for ADB 6.22.1.40 |
Placed the plcontainer Docker images (python2/python3) in our public registry |
Issue
It is impossible to add external ADB clusters to the general-purpose ADBM from the ADBM UI.
Workaround
-
Ensure the external ADB cluster with the installed ADBM service exists in ADCM.
-
Connect to the Linux console. Generate the Basic Authorization hash with base64 for a user with access to Arenadata DB Backup Manager via the following command:
echo -n <adbm_user>:<adbm_user_password> | base64
. For example:$ echo -n adbm_user:Password | base64
The result:
YWRibV91c2VyOlBhc3N3b3Jk
-
Send the following POST request to the general-purpose ADBM host:
-
Header parameters:
-
Accept
. -
Accept-Charset
. -
Authorization
. It should have the value started withBasic
and then the base64 value from the step 1. -
Content-Type
. -
X-ADBM_USER
. It should have theadbm_user
value from the step 1.
-
-
Body:
{ "clusterName": "<name of external ADB cluster in ADCM>", "clusterType": "<purpose of ADB cluster>", "clusterVersion": "<version of ADB cluster>" }
The following is an example of the POST request with the Linux
curl
command:$ curl --request POST \ --url http://adbm-main:8890/backend/adbm/api/v1/clusters \ --header 'Accept: application/json' \ --header 'Accept-Charset: ISO-8859-1' \ --header 'Authorization: Basic YWRibV91c2VyOlBhc3N3b3Jk' \ --header 'Content-Type: application/json' \ --header 'X-ADBM-USER: adbm_user' \ --data '{ "clusterName": "adb-demo", "clusterType": "ADB demo stand", "clusterVersion": "6.22"}'
A successful response contains a JSON with the generated identifier of an external cluster in ADBM. The cluster becomes visible in Arenadata DB Backup Manager → Clusters with Down status.
-
-
In ADCM, go to the external ADB cluster and select Services → ADBM → Configuration.
-
Set the Advanced flag and edit the ADBM agent service configuration parameter
ADBM_EUREKA_CLIENT_SERV_URL_DEF_ZONE
located in the bottom area. Replace its value with URL of the service registry for a general-purpose ADBM host, e.g.http://adbm-main:8761/eureka
. -
Apply the Reconfigure & Restart action to ADBM. Upon success, the cluster status in Arenadata DB Backup Manager → Clusters is changed to
Up
.
Date: 06.12.2022
Synced with upstream Greenplum Database 6.22.1 |
Upgraded gpbackup to 1.26.0.7 |
Upgraded PXF to 6.4.2.4 |
Upgraded kafka-adb to 0.16 |
Added encryption 1.0.0 |
Added adbm 1.0.0 |
Upgraded geospatial to 2.5.4.1 |
ADB bundle: implemented the |
ADB bundle: added the ADBM service and the ADBM configuration page |
ADB bundle: added an option to the ADB configuration to store a Docker certificate for a trust self-signed registry |
Obfuscated |
Added the ability to deserialize AVRO messages in kafka-adb |
Implemented ADBCC 4.0.0 |
Added a new system for ADB binary backups management — Arenadata DB Backup Manager (ADBM) |
Made optimizations in |
The error occurred during the postgis extension upgrade in ADB 6.22.0 |
The |
Fixed the cross-slice interaction detection for subplans |
The error with Precheck and Check actions after ADB installation |
The ADBCC client did not re-register on the ADBCC server when Reconfigure & Restart was being applied |
PXF might not catch a malformed chunked encoded response |
The postmaster process could exhaust all signal slots under the intensive connections pressure |
PXF hung indefinitely when it executed queries using the |
Changed logic for ADB |
Issue | Workaround |
---|---|
There is a potential memory leak with specific queries affected by the gpperfmon engine. If you use queries against huge tables with UDF that generate inner per-tuple queries, you may experience the significant RAM consumption, and even get OOM errors. The example is the |
The possible solution is to switch off monitoring metrics (this operation requires cluster restart):
Remember that this workaround does not disable the ADBCC UI and Arenadata DB Backup Manager |
During installation of the encryption module, you get the following error: |
Copy the necessary library from /usr/lib/pxf/lib/:
|
If you upgrade your cluster to 6.22.1.40 with installed ADBCC and the |
|
If you upgrade your cluster to 6.22.1.40, remember that during this process the |
If you do not want to include the
|
6.22.0
Date: 20.10.2022
Synced with upstream Greenplum Database 6.22.0 |
Added support for AltLinux 8.4 SP. AltLinux 8.2 SP is now deprecated |
Added Data Domain Boost 1.0.0 (adb_ddboost_plugin) |
Upgraded gptkh to 0.14 |
Upgraded diskquota to 2.0.1 |
Upgraded PXF to 6.4.2.3 |
PXF: allowed setting of Oracle parallel instructions |
PXF: enabled a filter pushdown status in PXF JDBC logs |
Implemented ADBCC 3.7.0 |
PostgreSQL planner produced a bogus plan for queries against replicated tables with |
The |
Fixed the lost parameter |
Refactored Planchecker to use an external ADBCC database |
The Postmaster process might exhaust all signal slots under the intensive connections pressure |
gpbackup: fixed the metadata order so that now gprestore can restore functions after the tables that are used in functions as a returning type |
Fixed the projection of boolean qualifiers which attributes are not in the |
PXF refactoring:
|
Applying the |
entrydb processed wrong slot resetting on moving a query to a resource group |
A failure occurred when DynamicSeqScan had a subPlan |
Failed to exchange a partition with a table having a dropped column that the table was distributed by |
The |
gptkh: fixed fetching of the actual |
Added a registry URL and arenadata-enterprise repository to the bundle configuration |
6.21.1
Date: 30.08.2022
Synced with upstream Greenplum Database 6.21.1 |
Enabled core dump files for ADB processes |
Implemented ADBCC 3.6.0 |
Tkhemali could not process text fields with a new line character |
Read data stream is released now when a partition scan is over |
The |
|
|
|
Fixed a gang loss during running a transaction when |
A database process entry initialized a whole plan tree |
6.21.0
Date: 21.07.2022
Synced with upstream Greenplum Database 6.21.0 |
Implemented ADBCC 3.5.1 |
Optimized DML queries against partitioned tables to avoid further planning if a partition was pruned |
Excluded the gpmon background process from the shared memory user list |
Refactored the gpdb specific code for the dispatch result waiting |
Implemented a fallback to PostgreSQL for an empty target list in CTE producer |
Fixed the cross-slice interaction detection for subplans |
Copying subplans for partitions by a planner broke the subplans order |
gpinitsystem failed on a machine with a custom locale |
gptkh could not parse engine settings with a dot symbol |
kafka-adb: re-added kafka-client-2.5.0.jar to the kadb-fdw connector |
6.20.3
Date: 19.05.2022
Synced with upstream Greenplum Database 6.20.3 |
PXF: when the PXF service migrated, the rights to the directory were not being checked |
PXF: the |
The gpexpand_schema.tar archive was created in the directory /home/gpadmin and could overflow the space |
A compatibility platform was incorrect for community bundles in AltLinux |
6.20.1
Date: 11.04.2022
Synced with upstream Greenplum Database 6.20.1 |
PXF: added PXF 6.3.0 to the ADB bundle (with ability to upgrade from PXF 5.x) |
PXF: activated a PXF cluster sync command |
PXF: added the PXF bin directory to the |
PXF: added the ability to override data types mapping in external tables for PXF |
Added Tkhemali connector 1.0.1 with a lot of refactoring |
Added the Delete Tkhemali action |
Added the Delete Kafka-to-ADB action |
Added the Delete ADB-to-Kafka action |
Added the |
Implemented ADBCC 3.4.0 |
Made editing of /etc/hosts optional |
PXF: error with JDBC Hive when one of the fields was a reserved word |
GPORCA failed on assert during transformation |
The aggregate mode did not handle properly query finish commands from QD (Query Dispatcher) |
kafka-adb: the storage option for an offset table is set explicitly now to avoid overriding |
ADBCC installation failed if a cluster name consisted of more than one word |
Interleaving of the append-optimized partitioned table removal and the |
gptkh: fixed the |
Tkhemali: column names with spaces were not handled properly |
GPORCA produced invalid plans for CTE (Common Table Expression) with replicated tables |
GPORCA: the |
Monitor scripts were not added to crontab on the Activate Standby action |
Backend server was displayed as IP while agent was displayed as FQDN on the Version page |
6.19.3
Date: 09.03.2022
Synced with upstream Greenplum Database 6.19.3 |
Implemented ADBCC 3.3.1 |
6.19.1
Date: 17.02.2022
Synced with upstream Greenplum Database 6.19.1 |
Hid a server name in the HTTPS group ADBCC service |
Added ADB Loader tools for RHEL 8 |
Added the ability to deploy maintenance scripts for several databases |
Enabled the |
Added the Delete PXF action |
Implemented ADBCC 3.3.0 |
Moved the Disable firewall option to the cluster level from the ADB service |
Wrong column binding was used to extract values from a SharedScan node |
gptkh: the distributed table |
gptkh: an error in parsing settings for distributed tables |
Coordinator did not use quote escaping for GUC values when restored on QE |
The sshd option |
Built the docker-compose RPM package 1.29.2 |
Issue | Workaround |
---|---|
[6X issue 13067] Gradual memory leak on mirror segments |
Increase monitoring for memory consumption in a cluster and restart a cluster during the maintenance if possible. This issue will be patched in the next release |
6.18.2
Date: 20.12.2021
Synced with upstream Greenplum Database 6.18.2 |
[6X backport] Implemented |
[6X backport] Zero fill pages skipped by a force WAL switch |
Added Kafka ADB connector 1.0.4 |
Added plcontainer 2.1.5 |
Implemented ADBCC 3.2.5 |
Power: an unexpected subplans order caused |
6.18.0
Date: 18.11.2021
Implemented ADBCC 3.2.4 |
When accessing from an append-optimized table, Index returned the wrong result |
kafka-fdw: fixed garbage in output at least for the text format |
gpbackup handled an empty tables set for an incremental data backup properly |
gpbackup hung forever after it was interrupted |
Date: 12.11.2021
Synced with upstream Greenplum Database 6.18.0 |
gpbackup: added an explicit order of tables by using pg_class.relpages |
PXF: added the partitioning query support for Sybase |
Implemented ADBCC 3.2.2 |
The |
madlib on ppc64le arch is now included into a build |
gpbackup could dump the partitioned table data twice |
The |
6.17.2
Date: 07.09.2021
Synced with upstream Greenplum Database 6.17.2 |
Synced with PXF 5.16.3 |
Synced with gpbackup 1.21.0 |
Synced with gpbackup-s3-plugin 1.7.0 |
Added a build for Power8 LE platform (ppc64le arch) |
Implemented ADBCC 3.1.3 |
Issue | Workaround |
---|---|
madlib on Power8 (ppc64le arch) breaks a gpdb build |
No workaround. madlib is not included into a Power8 (ppc64le arch) build |
6.17.1
Date: 17.08.2021
Synced with upstream Greenplum Database 6.17.1 |
Implemented the ZSTD compression support for gpbackup |
adcc-extension: started to send a schema name in the Node message |
ADB bundle: external database connection for ADBCC |
Implemented ADBCC 3.1.0 |
kafka-fdw: segments failed after applying |
PostgreSQL query optimizer built a bad plan for replicated tables with indexes |
adcc-extension: the expected segment distributed transaction context was |
adcc-extension: there was no possibility to differ QueryStatus for slices executed on Master |
Power: a bogus compiler error during pg_upgrade compilation |
6.16.3
Date: 03.08.2021
Synced with upstream Greenplum Database 6.16.3 |
[6X backport] |
adcc-extension: started to retrieve and send an error text |
ADB bundle: defined adjustable parameters for ADBCC |
Implemented ADBCC 3.0.3 |
Fixed |
[6X backport] Restricted execution for multi-level correlated queries |
adcc-extension: |
Issue | Workaround |
---|---|
kafka-fdw of versions 0.11-0.12 (they were ported in 6.15.0.17) does not work correctly when a batch size exceeds |
Do not use a batch size larger than |
6.16.2
Date: 24.06.2021
Synced with upstream Greenplum Database 6.16.2 |
[6X Backport] Shrinking of relation segment files to zero on |
ADBCC: added JVM arguments for logging |
PXF: removed the tuple count check for JDBC queries |
gpbackup failed when foreign tables were present in the database since it tried to acquire a lock on a foreign table |
6.16.1
Date: 03.06.2021
Synced with upstream Greenplum Database 6.16.1 |
Implemented ADBCC 2.1.1 |
Kafka ADB Connector: allowed users to set custom librdkafka options |
[6X backport] GPORCA fails with |
[6X backport] The |
ADB bundle: set a netcat timeout for sending monitoring metrics in AltLinux |
The PartitionSelector mechanism did not return tuples in case of the type mismatch |
adcc-extension: unknown node with |
adcc-extension: a locally planned mark was lost in node status messages for queries with custom aggregate |
Wrong CCNTs for plans dispatched after InitPlans were executed |
Removed redundant |
An invalid variable specified in the segment directory path check in ADCM |
Issue | Workaround |
---|---|
The gpbackup utility of versions 1.20.1 - 1.20.4 does not work correctly when foreign tables are present in a database. Backup fails with the |
Replace the current gpbackup with version 1.20.0 which is included in ADB 6.13.0.12 |
6.15.0
Date: 28.04.2021
Added the |
Kafka ADB connector: implemented signal handlers to interrupt consuming |
Ported ADB to Alt Linux 8.2 |
[6X backport PR 11625] pg_rewind: avoided removing files from the log directory |
Invalid values in the |
Kafka ADB connector did not consider partitions empty when a query for their watermark offsets failed after a timeout |
[6X backport] GPORCA produced an incorrect plan for the |
Date: 24.03.2021
Synced with upstream Greenplum Database 6.15.0 |
Implemented switchover from Master to Standby via ADCM |
Kafka ADB connector: converting AVRO dates before UNIX epoch to the Greenplum Database representation |
Kafka ADB connector: the Greenplum Database representation of AVRO double numbers that have more than 6 digits after a radix point |
Kafka ADB connector: wrong interpretation for AVRO timestamps below zero |
6.14.1
Date: 03.03.2021
Synced with upstream Greenplum Database 6.14.1 |
Added a link to the home ADBCC page, which is activated when a logo is clicked |
Removed online loading of static resources from the ADBCC web interface |
Resource group waiting queue corruption |
The |
A cluster failed after the single segment host lost due to the FTS misbehavior |
A multiline text in the CSV output from gplogfilter was incorrect |
6.13.0
Date: 21.01.2021
Synced with upstream Greenplum Database 6.13.0 |
Supported auxiliary relations for append-optimized tables to be used by the pgstattuple extension to exactly estimate the bloat of those relations |
Tkhemali-connector: avoided the intermediate conversion to a byte array |
Removed the obsolete batching options in ADQM connector (since the |
Reduced logging of gpstate |
Greenplum Database failed after the developer GUCs of PostgreSQL being activated |
GPORCA optimizer built inefficient query plans |
Column-wise statistics target parameters did not apply to partitioning tables |
Error with gpactivatestandby when running it too fast after the Master power off |
Error in parsing decimal parts for time types |
Scaling applied incorrectly to decimal values with a length less than a precision |
Bumped to the latest version of additional components |
6.12.1
Date: 21.12.2020
Synced with upstream Greenplum Database 6.12.1 |
Added the offset function to Kafka connector |
Added the rest committed function to Kafka ADB connector |
Implemented the text format for Kafka ADB connector |
Provided the |
Supported AVRO logical types in Kafka ADB connector |
Switched to the new way of postgis installation |
Started to use |
ADBCC disk space usage troubles in case of core dumps |
The |
The |
The |
Wrong behavior with a grouping function |
An exclusive lock on any partitioned table locked the |
A server locked the |