This is the multi-page printable view of this section. Click here to print.
List of unresolved issues for this Vertica release version.
List of resolved bugs and fixes for all hotfixes in this Vertica release version.
Describes the new features introduced in this Vertica release, and provides references to detailed information in the documentation set.
Details all deprecated and removed functionality for this Vertica release version.
Vertica makes every attempt to provide you with an up-to-date list of significant known issues in each release. We will update this list as we resolve issues and as we learn of new issues.
Updated 07/21/2025
| Issue Key | Component | Description |
|---|---|---|
| VER-97978 | Installation Program | When upgrading from release 24.1.0-6 to 24.3.0-4, Vertica doesn't remove the libssl* and libcrypto* files from /opt/vertica/lib. |
| VER-93373 | Client Drivers - JDBC | The JDBC driver returns the octal values when retrieving the ARRAY (VARBINARY) data. |
| VER-78310 | Client Drivers - JDBC |
JDBC complex types return NULL arrays as empty arrays. For example, when executing this SQL statement: The array column the server returns will be: Because of the null values in the string literal, it should return this value: This is a work around to a limitation in Simba. |
| VER-78074 | Procedural Languages, UDX | Stored procedures that contain DML queries on tables with key constraints do not return a value. |
| VER-61069 | Execution Engine | In very rare circumstances, if a Vertica process crashes during shutdown, the remaining processes might hang indefinitely. |
Updated 07/21/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 4343530 | Client Drivers - ODBC | The Vertica ODBC driver version 12 has been updated to resolve an issue where the driver incorrectly referenced the internal path for XML error message files. |
| 4344687 | Execution Engine | The LISTAGG function in Vertica versions prior to 12.0.2 exhibited significantly higher memory consumption when used with the WITHIN GROUP BY clause compared to its usage without the clause. This issue has been resolved. Memory consumption with and without the WITHIN GROUP BY clause is now more consistent. |
| 4346508 | Client Drivers - VSQL | From Vertica 9.3, file names with special characters are in the UTF-8 format. If there are issues loading files with special characters in their names, ensure that the encoding, code page, and locale settings are configured to support UTF-8. |
| 4347669 | Client Drivers - VSWL | There was an issue where the VSQL option '-v AUTOCOMMIT=ON' was not functioning as expected in Vertica v24.1. This release resolves the problem, ensuring that autocommit is properly enabled when specified via the -v option in VSQL. |
| 4348576 | UI - Management Console | The issue where users were unable to configure resource pool alerts in the Management Console (MC) has been resolved. |
| 4348822 | Machine Learning | Fixed an issue where the imported TensorFlow model required an unexpected number of input columns (64 instead of 6) during prediction. The model now correctly processes the expected 6 input features as defined in its metadata (tf_model_desc.json) and model summary. |
| 4348832 | Catalog Engine, Tuple Mover | During periods of TM activity, latency of some queries could increase due to catalog contention. The issue has been fixed. |
| 4349204 | Monitoring, UI - Management Console | Users were unable to create new resource pool alerts in the Management Console (MC) version 24.x. Clicking the Create Alert button resulted in no response, preventing the creation of new resource pool alerts. This issue has now been resolved. |
| 4358594 | License | Resolved an overflow issue in the calculation of the standard deviation for flex data size estimation. The fix ensures accurate calculation of variance and standard deviation, preventing NaN (not a number) values. |
| 4393207 | License | Table error_messages used to frequently contain warning message entries with a description similar to: "Skipping node information due to: Unknown node_id". This message did not indicate a real problem, so it was removed. |
| 4393228 | UI - Management Console | This release addresses MC vulnerabilities identified using the 'BlackDuck' tool. |
| 4404852 | Execution Engine | In corner cases in large JSON files where there were escape characters in string fields, a parsed string value could miss a few characters. This issue has been resolved. |
| 4405855 | Kafka Integration | An issue was causing nodes to crash after upgrading to Vertica 25.1, due to librdkafka assertion failures. This issue has been resolved. |
| 4415991 | Data load / COPY | An issue existed where the health check indicated a healthy state, even when MEMORY_PUSHBACK was blocking transactions, leading to application errors. This issue has been resolved. The cluster health check now provides a reliable indication of the cluster's ability to process transactions, allowing for proactive identification and resolution of memory pressure issues. |
| 4417061 | Kafka Integration | An issue was fixed, where the Kafka scheduler creation failed on both FIPS and non-FIPS systems after upgrading to Vertica v25.1. |
| 4434789 | Catalog Engine | A fix has been implemented to address an issue where the system experienced node crashes due to the failure to acquire a global catalog X lock (GCLX) during commit operations, specifically affecting insert statements. |
| 4636142 | Execution Engine | A node failure issue, that was triggered by a PANIC resulting from a fatal signal SIGSEGV after upgrading to version vertica-25.1.0, has been resolved. The fix includes a resolution for the panic message observed in the vertica.log. |
| 4534894 | Depot | The ANTI_PIN policy has been updated to avoid downloading files when possible. Previously, files marked with ANTI_PIN were downloaded and then immediately evicted, which could clog the fetcher queue and consume unnecessary resources. |
| 4634897 | Data Collector | Resolved an issue where comments added to table columns were not being updated in the jdbc_columns table. This update ensures that column remarks in jdbc_columns accurately reflect comments added to the corresponding table columns. |
| 4636142 | Execution Engine | A node failure issue, that was triggered by a PANIC resulting from a fatal signal SIGSEGV after upgrading to version vertica-25.1.0, has been resolved. The fix includes a resolution for the panic message observed in the vertica.log. |
| 4644416 | Execution Engine | Certain complex queries using internal temp relations in their plans could either error or output duplicate rows. This issue has been fixed. |
| 4686545 | Kubernetes | Fixed an issue where the VerticaDB Operator experienced deployment problems on Kubernetes when using IPv6. The operator would get into a loop attempting to restart pods, incorrectly detecting that Vertica was not started. |
| 4716237 | Node Management Agent, Vcluster | Critical security vulnerabilities have been identified and fixed in the Go binaries (vcluster, vcluster_server, and node_management_agent) that shipped with the Vertica database (both RPM and containers). |
| 4725483 | Kubernetes | Fixed an issue where creating a Vertica restore point would fail when the database was created using initpolicy set to Revive. |
| 4755533 | Admin Tools |
The following security vulnerabilities in the Python packages bundled with Vertica have been resolved: CVE-2024-39689: Upgrade Certifi to version 2024.07.04 or higher.
|
| 47700789 | SDK-Python | This release includes a critical security update, upgrading the Vertica Python version to 3.13.1 to address CVE-2024-9287. |
| 4778116 | Data load / COPY | Fixed a Vertica node crash that occurred when loading JSON data where some files contained data for ARRAY columns while others did not. The issue was triggered during COPY operations using the fjsonparser. |
| 4813336 | UI - Management Console | Fixed an issue in the Vertica Management Console where the License tab was displaying an error message and inaccurate license information. This issue has been resolved. |
| 4855456 | Catalog Engine | Fixed a node crash issue that occurred when running ALTER TABLE commands. The crash was triggered by a VAssert error (!inParentCatalog || (inParentCatalog && parent)) within the TieredCatalog component. This issue has been resolved to prevent unexpected node failures during ALTER TABLE operations. |
| 4858080 | Security | Fixed a bug where roles revoked from a user in Keycloak were not being revoked in Vertica after the user authenticated with an OAuth token. |