25.2.x Resolved issues¶
25.2.0-8¶
Updated 04/28/2026
25.2.0-7¶
Updated 04/21/2026
| Issue Key | Application Module | Description |
|---|---|---|
| 5297495 | Admin Tools | This update resolves multiple critical and high-severity security vulnerabilities, including CVE-2025-68121, CVE-2024-37298, CVE-2025-61726, CVE-2025-61728, CVE-2025-61730, CVE-2025-66418, CVE-2025-66471, CVE-2026-21441, CVE-2026-24049, and CVE-2026-26007. These issues were identified in version 23.4.0-23 and have been remediated to enhance system security. 此更新解决了多个严重和高危安全漏洞，包括 CVE-2025-68121、CVE-2024-37298、CVE-2025-61726、CVE-2025-61728、CVE-2025-61730、CVE-2025-66418、CVE-2025-66471、CVE-2026-21441、CVE-2026-24049 和 CVE-2026-26007。这些问题在 23.4.0-23 版本中被发现并已修复以增强系统安全性。 |
| 5331911 | Backup/DR | This update optimizes the load_snapshot() operation to significantly reduce execution time. Previously, redundant CRC checks for existing storage bundles and repeated storage location verifications for Storage Containers could cause delays of up to 4 hours. This fix streamlines these processes, resulting in a more efficient and faster snapshot loading experience.此更新优化了 load_snapshot() 操作以显著减少执行时间。此前，对现有存储 bundle 的冗余 CRC 检查以及存储容器的重复存储位置验证可能导致长达 4 小时的延迟。此修复简化了这些过程，实现了更高效、更快速快照加载体验。 |
| 5333791 | Backup/DR | Tombstone objects can have empty locations if queued after an upgrade from version 23.4 and older. For these, we now use the default storage location to avoid possible SIGSEGV. 墓碑对象在从 23.4 及更早版本升级后入队时可能具有空位置。对于这些情况，我们现在使用默认存储位置以避免可能的 SIGSEGV 错误。 |
25.2.0-6¶
Updated 03/20/2026
| Issue Key | Application Module | Description |
|---|---|---|
| 4837348 | Execution Engine | Certain complex queries using internal temp relations in their plans could either error or output duplicate rows. This issue has been resolved. 某些在计划中使用内部临时关系的复杂查询可能出现错误或输出重复行。此问题已解决。 |
| 4866836 | 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. 修复了运行 ALTER TABLE 命令时的节点崩溃问题。崩溃由 TieredCatalog 组件中的 VAssert 错误（!inParentCatalog |
| 4989561 | Execution Engine | An issue was found, where a node crash was triggered by a VAssert failure related to memory allocation, specifically 'VAssert(toCheckCleared[0] == 0 && (memSize < 16 || toCheckCleared[1] == 0)) failed'. This fix addresses the underlying memory management issue to prevent node crashes in similar scenarios. 发现了一个问题，与内存分配相关的 VAssert 失败触发了节点崩溃，具体为 VAssert(toCheckCleared[0] == 0 && (memSize < 16 |
| 5016484 | Admin Tools | Previously, running admintools -t logrotate --help displayed an incorrect usage message showing Usage: logrotateconfig [options], even though the actual tool name logrotateconfig was invalid. This caused confusion for users referencing the AdminTools documentation. The issue has been fixed — the help output now correctly shows: Usage: logrotate [options] along with the valid options list.此前，运行 admintools -t logrotate --help 显示错误的使用信息，显示为 Usage: logrotateconfig [options]，尽管实际工具名称 logrotateconfig 是无效的。这给参考 AdminTools 文档的用户带来了困惑。此问题已修复——帮助输出现在正确显示：Usage: logrotate [options] 以及有效选项列表。 |
| 5080225 | Execution Engine | Replicated tables used to error out when performing cross namespace ILM operations. This issue has been resolved. 复制表在执行跨命名空间 ILM 操作时曾出现错误。此问题已解决。 |
| 5084591 | Backup/DR | Fixed an issue where server-based replication between two Eon Mode clusters failed due to mismatched shard boundaries after migrating from an Enterprise Edition (EE) cluster to an Eon mode cluster. Replication now functions correctly between migrated and freshly installed clusters. 修复了从 Enterprise Edition（EE）集群迁移到 Eon 模式集群后，由于分片边界不匹配，两个 Eon 模式集群之间的基于服务器的复制失败的问题。复制现在可在迁移后的集群和新安装的集群之间正常运行。 |
| 5086371 | Data Networking | Addressed a potential deadlock scenario where TS callback destructors were executing while holding a lock. This could lead to conflicts with other system components, such as the async Messenger notifier, which might also require the same lock. The system has been updated to ensure that TS callback destructors now execute outside of the lock, thereby preventing deadlocks and improving overall system stability. 解决了 TS 回调析构函数在持有锁时执行可能导致死锁的问题。这可能与也可能需要同一锁的其他系统组件（如异步 Messenger 通知器）发生冲突。系统已更新，确保 TS 回调析构函数在锁外执行，从而防止死锁并提高整体系统稳定性。 |
| 5087105 | Data Networking | A high-severity issue where the Vertica database would hang shortly after upgrading to version 25.3.0-2, particularly when MinTLSVersion was set to 3, has been resolved. This fix, included in release VER 25.3.0-5, ensures database stability and prevents SQL queries from becoming stuck on all nodes, restoring normal operation.已解决一个高危问题，即 Vertica 数据库在升级到 25.3.0-2 后不久会挂起，特别是在 MinTLSVersion 设置为 3 时。此修复包含在 25.3.0-5 版本中，确保数据库稳定性并防止所有节点上的 SQL 查询卡住，恢复正常操作。 |
| 5093600 | Backup/DR | Int-String comparison in table expression used to fail VBR and VBR5 restore. This issue has been fixed. 表表达式中的整数字符串比较曾导致 VBR 和 VBR5 恢复失败。此问题已修复。 |
| 5105439 | UI - Management Console | The Management Console has been updated to no longer query the EnableSSL configuration parameter, eliminating the daily error messages and false alarms.Management Console 已更新，不再查询 EnableSSL 配置参数，消除了每日的错误消息和误报。 |
| 5107271 | Optimizer | Resolved an issue where UPDATE statements, when joining with multi-level views (views referencing other views and tables across different schemas), could incorrectly trigger an 'Internal Optimizer Error (11)'. Update queries involving these complex view structures now execute as expected without error.解决了 UPDATE 语句在与多层视图（引用其他视图和跨不同 Schema 的表的视图）连接时可能错误触发「内部优化器错误（11）」的问题。涉及这些复杂视图结构的更新查询现在可按预期正常执行。 |
| 5108701 | System: Performance | This fix involved changing how we track scan columns for the general case vs. in a database that has been resharded. In v11.1, the resharding feature added tracking of segmentation columns to all scans, even when they are not needed - the fix was to only track the segmentation columns if they are specifically needed for the query or for a reshard scenario. 此修复更改了在一般情况与重新分片数据库中跟踪扫描列的方式。在 v11.1 中，重新分片功能在所有扫描中都添加了分段列跟踪，即使不需要时也是如此。修复方案是仅在查询或重新分片场景特别需要时才跟踪分段列。 |
| 5143061 | Supported Platforms | Several critical and high-severity security vulnerabilities (e.g., CVE-2025-58183, CVE-2025-58186, CVE-2025-58187 in stdlib) within the vertica-23.4.0-21.x86_64.SUSE.rpm package have been remediated.已修复 vertica-23.4.0-21.x86_64.SUSE.rpm 包中的多个严重和高危安全漏洞（例如 stdlib 中的 CVE-2025-58183、CVE-2025-58186、CVE-2025-58187）。 |
| 5159224 | Execution Engine | Vertica was not be able to process queries with a user defined function in an array. Now it handles this case as expected without risk of crash (in the worst case scenario). Vertica 无法处理数组中包含用户自定义函数的查询。现在它能够按预期处理此情况，而不会有崩溃风险（在最坏情况下）。 |
| 5177723 | DDL - Table | This fix resolves an issue where temporary relation (TempRel) decoding could lead to data corruption, specifically affecting string data within recursive Common Table Expressions (CTEs). The fix ensures proper handling of character encoding and VARCHAR length constraints, preventing the occurrence of non-UTF8 data and oversized strings, thereby restoring data integrity and eliminating the need for performance-impacting workarounds.此修复解决了临时关系（TempRel）解码可能导致数据损坏的问题，特别影响递归公用表表达式（CTE）中的字符串数据。修复确保正确处理字符编码和 VARCHAR 长度约束，防止出现非 UTF8 数据和超长字符串，从而恢复数据完整性并消除影响性能的临时解决方案。 |
| 5184561 | Admin Tools | Before this release, AdminTools restart_node may find a secondary UP node to run catalog editor for getting catalog information. After this fix, AdminTools restart_node consistently finds a primary UP node to run catalog editor for getting catalog information, this ensures the getting the correct and up-to-date catalog information. 在此版本之前，AdminTools restart_node 可能选择辅助 UP 节点来运行目录编辑器以获取目录信息。此修复后，AdminTools restart_node 始终选择主 UP 节点来运行目录编辑器以获取目录信息，确保获取正确且最新的目录信息。 |
| 5196647 | Execution Engine | An enhancement was added in version 24.1 which preserved the outer's sortedness for hash/merge right outer joins, if it was compatible. With this ticket, we saw that it is possible in a merge join for that enhancement to result in a sort violation (which can create inconsistent results with aggregate functions, as in this case). In order to maintain the sort, we added back the explicit Sort path when we're dealing with a merge join. 24.1 版本新增了一项优化，在兼容的情况下保留哈希/合并右外连接的外表排序。在此工单中，我们发现合并连接中该优化可能导致排序违规（在本例中会在使用聚合函数时产生不一致的结果）。为保持排序，我们在处理合并连接时恢复了显式排序路径。 |
| 5202439 | Execution Engine | Previously when a user using the COPY command with the delimited parser was trying to insert data for an array[varchar] column, they could trigger an internal error if their input began with back-to-back enclosing characters. Now, the server appropriately can parse multiple enclosing characters to begin an array[varchar] column, where the first enclosing character is treated as an enclosing character and the second enclosing character represents the first character in the varchar data. 此前，用户使用带有分隔符解析器的 COPY 命令尝试为 array[varchar] 列插入数据时，如果输入以连续封闭字符开头，可能触发内部错误。现在，服务器能正确解析多个连续封闭字符以开始 array[varchar] 列，其中第一个封闭字符被视为封闭字符，第二个封闭字符表示 varchar 数据中的第一个字符。 |
| 5203746 | Kafka Integration | This update addresses a critical security vulnerability, CVE-2025-68161, found in org.apache.logging.log4j_log4j-core version 2.17.1. The vulnerability was identified during Prisma scans on container_minimal_arm environments. The Log4j core library has been upgraded to version 2.25.3 to mitigate this issue.此更新修复了在 container_minimal_arm 环境 Prisma 扫描中发现的 org.apache.logging.log4j_log4j-core 版本 2.17.1 中的严重安全漏洞 CVE-2025-68161。Log4j 核心库已升级至 2.25.3 版本以缓解此问题。 |
| 5206360 | Catalog Engine | Concurrent sequence generation in OCC lock mode can now tolerate LockTimeout setting to zero. Instead of immediate failing, they now wait for the maximum amount of time given by LockTimeout and a new knob called MinOCCLockTimeout.OCC 锁定模式下的并发序列生成现在可以容忍 LockTimeout 设置为零。它们不再立即失败，而是等待 LockTimeout 和新参数 MinOCCLockTimeout 所指定的最长时间。 |
| 5211012 | EON | We used to determine the transaction log size based off a wrong counter hence truncating a corrupted transaction file more than necessary. We now use a right counter to store the size hence truncating the last transaction file correctly. 此前我们基于错误的计数器确定事务日志大小，导致截断了比必要更多的损坏事务文件。我们现在使用正确的计数器来存储大小，从而正确截断最后一个事务文件。 |
| 5214187 | S3 | Previously, the S3 layer could incorrectly count streaming connections, potentially leading to connection pool exhaustion during high S3 request surges. This could block S3 read operations and queries, including critical services like TxnLogSync. This fix ensures streaming connections are counted properly and limits are enforced, preventing connection starvation and improving S3 read reliability.此前，S3 层可能错误地计数流式连接，在 S3 请求激增时可能导致连接池耗尽。这会阻塞 S3 读取操作和查询，包括 TxnLogSync 等关键服务。此修复确保流式连接被正确计数并强制执行限制，防止连接枯竭并提高 S3 读取可靠性。 |
| 5222230 | AMI | Queries failing due to network errors in EE's Data Target Proxy are now retryable, allowing the Vertica server to mitigate such failures with its retry mechanism. 由于 EE 的 Data Target Proxy 中网络错误而失败的查询现在支持重试，允许 Vertica 服务器通过其重试机制缓解此类故障。 |
| 5224614 | Optimizer | Previously, nodes could be brought down by executing a MERGE query when a target value of the INSERT statement was a subquery. Now, a proper error message is displayed when this is attempted which is in line with the restrictions for using a subquery as a value for an INSERT statement outside of a MERGE query. 此前，当 MERGE 查询中 INSERT 语句的目标值为子查询时，可能导致节点宕机。现在，执行此操作时会显示正确的错误消息，与在 MERGE 查询外部使用子查询作为 INSERT 语句值时的限制一致。 |
| 5225289 | Kubernetes, Vcluster | Before the fix, Kubernetes operator may error out upon seeing remote user storage location when reviving an Eon mode database migrated from a 10.x Enterprise database. Now, Kubernetes operator correctly handles the remote user storage locations created in an old version enterprise database for reviving. 修复前，Kubernetes operator 在恢复从 10.x Enterprise 数据库迁移的 Eon 模式数据库时，遇到远程用户存储位置可能会报错。现在，Kubernetes operator 能正确处理旧版本 Enterprise 数据库中创建的远程用户存储位置以进行恢复。 |
| 5225681 | Optimizer | This release addresses an 'Internal Optimizer Error (11)' that could occur when executing complex SQL queries involving Common Table Expressions (CTEs) and UNION operations. The error was observed in scenarios where the EnableWITHTempRelReuseLimit parameter was set to its default value or higher, leading to query failures. Previously Affected Versions: Vertica v25.1.0-0, v24.4.0-0, v23.4.0-14, and earlier. Workaround (prior to this fix): Users could mitigate the issue by setting the EnableWITHTempRelReuseLimit configuration parameter to 0 or 5. This issue is now resolved, allowing such queries to execute successfully without requiring parameter adjustments.此版本解决了执行涉及公用表表达式（CTE）和 UNION 操作的复杂 SQL 查询时可能出现的「内部优化器错误（11）」。在 EnableWITHTempRelReuseLimit 参数设置为默认值或更高值时观察到该错误，导致查询失败。先前受影响的版本：Vertica v25.1.0-0、v24.4.0-0、v23.4.0-14 及更早版本。临时解决方案（在此修复之前）：用户可以通过将 EnableWITHTempRelReuseLimit 配置参数设置为 0 或 5 来缓解该问题。此问题现已解决，允许此类查询成功执行，无需调整参数。 |
| 5232013 | Node Management Agent, Vcluster | This update addresses multiple security vulnerabilities, including critical and high severity CVEs, identified in the Golang binaries shipped with Vertica 26.1.0-0 container images. These vulnerabilities previously impacted deployment in Kubernetes environments utilizing vulnerability-based admission controllers. The fix enhances the security posture of Vertica container images and ensures compliance for seamless integration and deployment. 此更新解决了 Vertica 26.1.0-0 容器镜像中随附的 Golang 二进制文件中发现的多个安全漏洞，包括严重和高危 CVE。这些漏洞此前影响在 Kubernetes 环境中使用基于漏洞的准入控制器的部署。此修复增强了 Vertica 容器镜像的安全性并确保集成和部署的合规性。 |
| 5244104 | Optimizer | In some cases, analyze statistics could encounter internal type mismatches when processing projections causing an Optimizer assert failure. The cause of these mismatches has been resolved. 在某些情况下，analyze_statistics 在处理投影时可能遇到内部类型不匹配，导致优化器断言失败。此问题已解决。 |
| 5256912 | Execution Engine | Resolved a critical defect where the Vertica server (v25.2.0-3) would crash unexpectedly with a SIGSEGV error when executing queries involving the ~ ANY (Subquery) construct. This issue led to database unavailability.This fix addresses the underlying cause of the server crash, ensuring stability and preventing database panics when using ~ ANY (Subquery) in queries.解决了一个关键缺陷：Vertica 服务器（v25.2.0-3）在执行涉及 ~ ANY (Subquery) 结构的查询时，会因 SIGSEGV 错误意外崩溃。此问题导致数据库不可用。此修复解决了服务器崩溃的根本原因，确保在使用 ~ ANY (Subquery) 查询时的稳定性。 |
| 5266217 | Optimizer | In some cases, union sub-queries with coercion could result in type conflicts and an internal error. This has been resolved. 在某些情况下，包含类型转换的 union 子查询可能导致类型冲突和内部错误。此问题已解决。 |
25.2.0-5¶
Updated 12/05/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 4878505 | System: Performance | Fix for 100% CPU Utilization with STRPOS Function: We’ve optimized the behavior of the STRPOS function to significantly improve performance in specific scenarios. What changed: Previously, all inputs to STRPOS were converted to UTF-16 to leverage the ICU (International Components for Unicode) library for string comparison. While ICU provides robust support for complex locale-aware comparisons, this conversion introduced overhead—especially for simple use cases. Now, for simple locales with 1-to-1 character mappings (such as en_US, de_DE, and other locales where each character maps directly between UTF-8 and UTF-16 without requiring normalization or multi-codepoint handling), STRPOS uses a UTF-8 based comparison. This avoids the need for conversion to UTF-16 and bypasses the ICU library entirely, resulting in much faster execution. 修复 STRPOS 函数导致 100% CPU 使用率的问题：我们优化了 STRPOS 函数的行为，显著提升了特定场景下的性能。变更内容：此前，所有 STRPOS 的输入都被转换为 UTF-16 以利用 ICU 库进行字符串比较。现在，对于具有 1 对 1 字符映射的简单区域，STRPOS 使用基于 UTF-8 的比较，避免了转换为 UTF-16 并完全绕过了 ICU 库，从而实现更快的执行速度。 |
| 4970328 | Security | Fixed an issue where creating access policies added extra parentheses, causing COPY_TABLE to fail with an access policy mismatch error. 修复了创建访问策略时添加了额外括号，导致 COPY_TABLE 因访问策略不匹配错误而失败的问题。 |
| 4990343 | Execution Engine | An issue occurred where LISTAGG queries did not consistently return NULL when no rows match the search criteria. This bug manifested when using the WITHIN GROUP clause alongside an AND NOT EXISTS subquery within the LISTAGG statement. This issue has been resolved. 修复了 LISTAGG 查询在无行匹配搜索条件时未一致返回 NULL 的问题。此错误在使用 WITHIN GROUP 子句以及在 LISTAGG 语句中使用 AND NOT EXISTS 子查询时出现。此问题已解决。 |
| 5004898 | EON | This release addresses an issue where cluster nodes experienced frequent crashes due to out-of-memory (OOM) errors. The problem was observed across primary and secondary subclusters, with RSS memory usage growing constantly, even on idle secondary subclusters. The fix resolves a memory leak that was affecting all hosts, regardless of hardware specifications or operating system. 此版本解决了集群节点因内存不足（OOM）错误频繁崩溃的问题。此问题在主从子集群中均有观察到，RSS 内存使用持续增长，即使空闲的从子集群也是如此。此修复解决了影响所有主机的内存泄漏问题。 |
| 5011525 | Security | New Database Parameter: Introduced a new database parameter, OAuth2JITConflictPolicy, to control OAuth2 JIT login for existing users. MERGE, the default, allows OAuth2 login for existing vertica users and grants them the appropriate auth method. This is identical to the existing behavior. If set to IGNORE then existing users require an OAuth2 client authentication granted to log in with an OAuth2 token, no automatic granting is performed. Users with psuedosuperuser are always treated as if OAuth2JITConflictPolicy is set to IGNORE, ie. they can only use authentication methods that have been explicitly granted. 新增数据库参数：引入了新的数据库参数 OAuth2JITConflictPolicy，用于控制现有用户的 OAuth2 JIT 登录。MERGE（默认值）允许现有 Vertica 用户进行 OAuth2 登录并授予其相应的认证方法。设置为 IGNORE 时，现有用户需要授予 OAuth2 客户端认证才能登录。 |
| 5040784 | Admin Tools | This fix ensures the upgrade process is successful and correctly handles the FlexTableLib library, resolving the fjsonparser incompatibility issue. 此修复确保升级过程成功并正确处理 FlexTableLib 库，解决了 fjsonparser 不兼容的问题。 |
| 5050270 | 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). 在 Vertica 数据库（RPM 和容器）附带的 Go 二进制文件（vcluster、vcluster_server 和 node_management_agent）中发现了关键安全漏洞并已修复。 |
25.2.0-4¶
Updated 09/30/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 4773235 | License | An issue occurred where license audit compliance status showed an anomaly. This issue has been resolved. The GET_COMPLIANCE_STATUS() function now accurately reflects the overall compliance status, aligning with individual schema audits. 修复了许可证审计合规状态显示异常的问题。此问题已解决。GET_COMPLIANCE_STATUS() 函数现在准确反映整体合规状态，与单个 Schema 审计保持一致。 |
| 4873509 | UI - Management Console | Fixed a defect where Vertica Management Console (MC) did not support SMTP configuration without authentication after Keycloak integration. The original email functionality has been restored to support SMTP configurations that do not require a username and password. 修复了 Vertica Management Console（MC）在 Keycloak 集成后不支持无认证 SMTP 配置的缺陷。原始电子邮件功能已恢复，支持不需要用户名和密码的 SMTP 配置。 |
| 4876454 | Optimizer | Fixed an issue where INSERT…SELECT statements would hang when GROUPBY PUSHDOWN was not occurring due to the presence of non-equi joins. The fix ensures that INSERT…SELECT queries with non-equi joins no longer result in indefinite hanging, restoring expected performance. 修复了由于非等值连接导致 GROUPBY PUSHDOWN 未发生时，INSERT...SELECT 语句挂起的问题。修复确保带有非等值连接的 INSERT...SELECT 查询不再无限挂起，恢复预期性能。 |
| 4893664 | Machine Learning | Resolved an issue where the imported TensorFlow model required an unexpected number of input columns (64) instead of the expected 6 (based on tf_model_desc.json and model summary). The model now correctly predicts with the expected number of input features. 解决了导入的 TensorFlow 模型需要意外数量的输入列（64 列而非预期的 6 列）的问题。模型现在能使用预期的输入特征数量进行正确预测。 |
| 4904024 | Hadoop, ResourceManager | Resolved an issue where upgrading from Vertica version 12.0.4 to 25.1 resulted in database startup failures due to timeouts. This issue occurred on replicated S3 buckets within a separate cluster running Rocky Linux 8.10. The fix addresses a signal 11 error encountered during the 'Read DataCollector' stage of the startup process, specifically related to refreshing disk space information. 解决了从 Vertica 12.0.4 升级到 25.1 时因超时导致数据库启动失败的问题。此问题发生在单独集群中运行 Rocky Linux 8.10 的复制 S3 存储桶上。修复解决了启动过程中「Read DataCollector」阶段遇到的信号 11 错误，特别是与刷新磁盘空间信息相关的部分。 |
| 494350 | UI - Management Console | This fix addresses security vulnerabilities in Tomcat and Spring Security by upgrading Tomcat to version 10.1.42 and Spring Security to version 6.4.4. 此修复通过将 Tomcat 升级到 10.1.42 和 Spring Security 升级到 6.4.4 来解决 Tomcat 和 Spring Security 的安全漏洞。 |
| 4950424 | Data load / COPY | Fixed a node down issue that occurred when the 'CopyFaultTolerantExpressions' parameter was enabled and FILLER was used in conjunction with specific TO_CHAR format strings. This fix prevents unexpected node failures during COPY operations using TO_CHAR with FILLER. 修复了启用 CopyFaultTolerantExpressions 参数且 FILLER 与特定 TO_CHAR 格式字符串一起使用时节点宕机的问题。此修复防止了在使用 TO_CHAR 和 FILLER 的 COPY 操作期间出现意外节点故障。 |
| 4959200 | Cloud - Amazon | Fixed an issue where nodes would experience 'ExpiredToken' errors when reading from Parquet files in S3, leading to catalog truncation lag and requiring node restarts. The issue was caused by the system not properly refreshing AWS IAM role credentials. This fix ensures the system correctly handles token expiration and refreshes credentials as needed, preventing disruption to business operations. 修复了节点在从 S3 读取 Parquet 文件时遇到「ExpiredToken」错误，导致目录截断滞后并需要重启节点的问题。此问题由系统未正确刷新 AWS IAM 角色凭据引起。此修复确保系统正确处理令牌过期并按需刷新凭据，防止业务运营中断。 |
25.2.0-3¶
Updated 07/03/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 4860219 | UI - Management Console | An issue where N2 series machines were not visible in the MC provisioning tool for GCP's us-east4-c region, despite being available in the GCP console and documented as supported, has been resolved. Users can now provision N2 series machines via MC in the specified region. 解决了在 GCP 的 us-east4-c 区域中 N2 系列机器在 MC 配置工具中不可见的问题，尽管它们在 GCP 控制台中可用且文档支持。用户现在可以通过 MC 在指定区域配置 N2 系列机器。 |
25.2.0-2¶
Updated 06/14/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 4811711 | Data load / COPY | In specific scenarios involving large JSON files with escape characters in string fields, the parsed string value could be missing a few characters. This issue has been resolved. 在涉及大型 JSON 文件且字符串字段中包含转义字符的特定场景中，解析后的字符串值可能缺少几个字符。此问题已解决。 |
| 4815847 | 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. 从 Vertica 9.3 开始，包含特殊字符的文件名采用 UTF-8 格式。如果加载带有特殊字符文件名的文件时出现问题，请确保编码、代码页和区域设置已配置为支持 UTF-8。 |
25.2.0-1¶
Updated 05/22/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 4534858 | Catalog Engine, Tuple Mover | A performance degradation that occurred after upgrading from 12.0.4 to 24.3.x and 24.4.0-0 has been resolved. 解决了从 12.0.4 升级到 24.3.x 和 24.4.0-0 后出现的性能下降问题。 |
| 4535429 | 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 and thus has been removed. 表 error_messages 中经常包含描述类似「跳过节点信息，原因：未知 node_id」的警告消息条目。此消息并不表示真正的问题，因此已被移除。 |
| 4634967 | Kafka Integration | There was a keystone configuration issue where the Kafka scheduler could not be created on Vertica 25.1 systems, regardless of whether they were running in FIPS mode or not. This issue has been resolved. 存在一个 keystone 配置问题，导致 Kafka 调度程序无法在 Vertica 25.1 系统上创建，无论系统是否运行在 FIPS 模式下。此问题已解决。 |
| 4753286 | Third Party Tools Integration | Issues identified in the node_management_agent and vcluster components of Vertica have been resolved. 已解决 Vertica 的 node_management_agent 和 vcluster 组件中发现的问题。 |
| 4753290 | Admin Tools | The following security vulnerabilities in the Python packages bundled with Vertica 25.2.0-1 have been resolved: - Certifi: The Certifi package has been upgraded to version 2024.07.04 or higher to address CVE-2024-39689. - WebOb: The WebOb package has been upgraded to version 1.8.8 or above to address CVE-2024-42353. - Mercurial: The Pip Mercurial package has been upgraded to address CVE-2023-5752. - Idna: The Inda package has been upgraded to version 3.7 to address CVE-2024-3651. 已解决 Vertica 25.2.0-1 随附的 Python 包中的以下安全漏洞：Certifi 包已升级到 2024.07.04 或更高版本以解决 CVE-2024-39689；WebOb 包已升级到 1.8.8 或更高版本以解决 CVE-2024-42353；Pip Mercurial 包已升级以解决 CVE-2023-5752；Idna 包已升级到 3.7 以解决 CVE-2024-3651。 |
| 4771895, 4771898, 4772161 | UI - Management Console, Security | Security vulnerabilities within a component library using the Spring framework have been remedied. 已修复使用 Spring 框架的组件库中的安全漏洞。 |
25.2.0¶
Updated 04/11/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 4336550 | Complex Types | An issue was fixed, where Vertica was unable to load Parquet files with two-level encoded arrays, resulting in the error "Source has unsupported ARRAY type at X." This enhancement enables Vertica to properly process Parquet files with this array structure, improving compatibility with external data sources. 修复了 Vertica 无法加载具有两级编码数组的 Parquet 文件的问题，报错「源在 X 处有不支持的 ARRAY 类型」。此增强使 Vertica 能够正确处理具有此数组结构的 Parquet 文件，提高了与外部数据源的兼容性。 |
| 4338772 | Scrutinize | An issue existed where Scrutinize wasn't collecting OS release information across various Linux distributions, including Debian, Ubuntu, Amazon Linux and SUSE Linux Enterprise. This issue has been resolved. 存在一个问题：Scrutinize 未收集各种 Linux 发行版（包括 Debian、Ubuntu、Amazon Linux 和 SUSE Linux Enterprise）的 OS 发布信息。此问题已解决。 |
| 4344794 | UDX | Creating user-defined extensions (UDX) in Python with the DEPENDS clause when the dependent libraries are present in Azure blob storage or Google cloud storage fails. This issue is now resolved. The value of maxNest is increased to 15 from a default value of 2. 在 Python 中使用 DEPENDS 子句创建用户自定义扩展（UDX）时，如果依赖库位于 Azure blob 存储或 Google 云存储中，则会失败。此问题现已解决。maxNest 的值从默认值 2 增加到 15。 |
| 4346275 | Optimizer | An issue was discovered where, under some conditions, queries to tables with partitions that include attributes in non-table order could error on statistic lookup. This issue has been resolved. 发现一个问题：在某些条件下，对包含非表顺序属性分区的表进行查询时，统计信息查找可能出错。此问题已解决。 |
| 4346342 | License | An issue was causing inaccurate database size estimations due to cache invalidation issues after node subscriptions changed (node restarts or failures), primarily affecting sample caching for license auditing. This issue has been resolved. 节点订阅更改（节点重启或故障）后的缓存失效问题导致数据库大小估计不准确，主要影响许可证审计的样本缓存。此问题已解决。 |
| 4347675 | Scrutinize | An issue was found, where 'save-system-table-as-parquet' option in Scrutinize corrupts directory names for exported system tables. This issue has been resolved by correcting the directory renaming logic, ensuring that the original directory names are preserved during the export process. Users can now reliably load the exported Parquet files without encountering directory name corruption. 发现 Scrutinize 中的「save-system-table-as-parquet」选项会损坏导出系统表的目录名。此问题已通过更正目录重命名逻辑得到解决，确保导出过程中保留原始目录名称。用户现在可以可靠地加载导出的 Parquet 文件而不会遇到目录名损坏。 |
| 4347993 | Backup/DR | The backup process has been updated to correctly handle scenarios where one or more Vertica nodes are down. Previously, backups could fail if a node was unreachable, even when specifying the '--nodes' option. This fix ensures that the backup process only attempts to connect to active nodes, resolving the issue. 备份过程已更新，能正确处理一个或多个 Vertica 节点宕机的场景。此前，即使指定了「--nodes」选项，如果节点不可达，备份也可能失败。此修复确保备份过程仅尝试连接到活动节点，解决了此问题。 |
| 4348000 | Execution Engine | The Vertica query parser now properly handles the use of PARTITION ROW and PARTITION LEFT JOIN in queries. Instead of returning internal errors, Vertica now rejects the syntax with an appropriate error message, similarly to how it handles other unsupported partition options like PARTITION AUTO, PARTITION BEST, and PARTITION NODES. This fix ensures that users receive clear and informative error messages when attempting to use unsupported partition options. Vertica 查询解析器现在能正确处理查询中使用 PARTITION ROW 和 PARTITION LEFT JOIN 的情况。Vertica 不再返回内部错误，而是以适当的错误消息拒绝该语法，与其处理其他不支持的分区选项（如 PARTITION AUTO、PARTITION BEST 和 PARTITION NODES）的方式类似。此修复确保用户在使用不支持的分区选项时收到清晰的信息性错误消息。 |
| 4348485 | Scrutinize, Vcluster | System table data retrieved using vcluster scrutinize now has column headers in the retrieved files. This enhancement ensures compatibility with database loading processes and tools like the grasp loader, which rely on these headers to identify columns. 使用 vcluster scrutinize 检索的系统表数据现在在检索到的文件中包含列标题。此增强确保与依赖这些标题识别列的数据库加载过程和工具（如 grasp loader）的兼容性。 |
| 4348547 | Directed Query | Directed query search could fail to match queries in cases where the predicate included constant-to-constant operations {{CONST op CONST.. This issue has been resolved, ensuring reliable query matching. 在谓词包含常量到常量操作 {{CONST op CONST}} 的情况下，定向查询搜索可能无法匹配查询。此问题已解决，确保可靠的查询匹配。 |
| 4348750 | Optimizer | Historically, the statistics histogram would be invalidated if the row count was updated without fully reanalyzing the columns; this invalidation no longer happens. 历史上，如果行计数更新而未完全重新分析列，统计信息直方图将失效；此失效情况已不再发生。 |
| 4348821 | Installation Program | An issue where installing Vertica on Amazon 2023 Linux fails and an error message is displayed has been resolved. 解决了在 Amazon 2023 Linux 上安装 Vertica 失败并显示错误消息的问题。 |
| 4349067 | Database Designer Core, Refresh | Fixed a bug that caused some refreshes to fail when the ancient history mark (AHM) was updated in the background. The refresh process now has priority in cases where AHM and Refresh conflict, ensuring successful completion. 修复了当后台更新 ancient history mark（AHM）时某些刷新失败的问题。在 AHM 和 Refresh 冲突的情况下，刷新过程现在具有优先级，确保成功完成。 |
| 4349129 | UI - Management Console | The 'DBD upload file permission error' has been resolved. Users can now successfully upload query files in the DBD tab, or via MC > New design > Manual, without encountering a 'Permission denied' error. This fix ensures that superusers, and all users, can upload files without permission restrictions. 「DBD 上传文件权限错误」已解决。用户现在可以在 DBD 选项卡或通过 MC > 新设计 > 手动成功上传查询文件，而不会遇到「权限被拒绝」错误。此修复确保超级用户和所有用户都可以上传文件而无需权限限制。 |
| 4349189 | Backup/DR | The garbage collection process was failing to clear unreferenced objects due to a 'file not found' error during the rebuild of the backup manifest. This issue has been resolved. 由于重建备份清单时出现「文件未找到」错误，垃圾回收过程无法清理未引用的对象。此问题已解决。 |
| 4349838 | Optimizer | Queries utilizing WITH statements, used on multiple query levels with different target lists on each level, would sometimes return an error. The issue has been resolved. 在多查询层级使用 WITH 语句且每层具有不同目标列表的查询有时会返回错误。此问题已解决。 |
| 4350031 | Data load / COPY | We have extended our Parquet parser to support the legacy LIST structures. 我们已扩展 Parquet 解析器以支持传统的 LIST 结构。 |
| 4350074 | Machine Learning | A fix has been implemented to address an issue encountered when importing XGBoost models in PMML format. Specifically, an error was triggered during the import process, resulting in a 'VIAssert' failure. This issue has been resolved to ensure successful PMML model imports. 已实施修复以解决导入 PMML 格式的 XGBoost 模型时遇到的问题。具体来说，导入过程中触发了 VIAssert 失败错误。此问题已解决，确保 PMML 模型成功导入。 |
| 4350099 | UI - Management Console | An issue with a potential cross-site scripting vulnerability has been resolved. 解决了潜在的跨站脚本漏洞问题。 |
| 4350134 | Admin Tools | Admintools was unable to stop a node on Debian. The issue was due to changes in the 'ps' command utility in Debian 12's procps package, and has now been resolved. Admintools 无法在 Debian 上停止节点。此问题是由于 Debian 12 的 procps 包中「ps」命令工具的变化引起的，现已解决。 |
| 4350653 | Admin Tools, Backup/DR, S3 | IMDSv2 support for config setup at db start has been added. 在数据库启动时添加了对 IMDSv2 配置设置的支持。 |
| 4391327 | Optimizer | A fix has been implemented to address an issue where the UNION operation was dropping TIMESTAMP precision. 已实施修复以解决 UNION 操作丢弃 TIMESTAMP 精度的问题。 |
| 4391353, 4391363, 4391364, 4391366 | DDL - Table | Upgrading or migrating from v23.4 (or older) to v24.1 (or newer) invalidates the reference_schema_id field in the system table vs_view_tables (sets it to 0). This issue has been resolved. 从 v23.4（或更早版本）升级或迁移到 v24.1（或更新版本）会使系统表 vs_view_tables 中的 reference_schema_id 字段失效（设为 0）。此问题已解决。 |
| 4392283 | Complex Types | When running an EXPLODE or UNNEST function in a locale with collation other than binary, Vertica would throw an error due to an improperly formatted OVER clause, even when the skip_partitioning parameter is set to true. This has been resolved; now, Vertica accepts the skip_partitioning parameter regardless of the current locale's collation. 在具有非二进制排序规则的区域设置中运行 EXPLODE 或 UNNEST 函数时，即使 skip_partitioning 参数设置为 true，Vertica 也会因 OVER 子句格式错误而抛出错误。此问题已解决；现在，Vertica 接受 skip_partitioning 参数，无论当前区域的排序规则如何。 |
| 4393179 | Catalog Engine | A fix has been implemented to address reported slowness of ETL jobs due to locks when taking new sequences, impacting performance. 已实施修复以解决因获取新序列时的锁导致 ETL 作业变慢、影响性能的问题。 |
| 4393180 | Execution Engine | Fixed an issue where executing ANALYZE_STATISTICS(' ') with a space as an argument would cause the node to go down. 修复了使用空格作为参数执行 ANALYZE_STATISTICS(' ') 导致节点宕机的问题。 |
| 4403837 | Security | There was an issue where S3 bucket credentials were not masked when using the SHOW CURRENT command, potentially exposing sensitive information. This issue has been resolved, ensuring that credentials are now properly hidden, maintaining data security. 存在一个问题：使用 SHOW CURRENT 命令时 S3 存储桶凭据未被掩码，可能暴露敏感信息。此问题已解决，确保凭据现在被正确隐藏，维护数据安全。 |
| 4403814 | Catalog Engine | A node crash caused by GCLX being held by Manage Epochs: Advance AHM has been resolved. 已解决由 Manage Epochs: Advance AHM 持有 GCLX 导致的节点崩溃。 |
| 4405841 | Backup/DR | An issue where the REPLICATE function fails in an EON mode setup when a node in a subcluster goes down during the replication process has been resolved. This fix ensures that the REPLICATE function is more resilient to node failures in subclusters during EON mode operations. 解决了在 EON 模式设置中，当子集群中的节点在复制过程中宕机时 REPLICATE 函数失败的问题。此修复确保 REPLICATE 函数在 EON 模式操作期间对子集群中的节点故障具有更强的弹性。 |
| 4446899 | EON | The UsePeerToPeerDataTransfer parameter can now be set at the subcluster level in Vertica. This enhancement allows users to reduce overhead from Peer-to-Peer (P2P) data transfer without disabling the feature at the database level, providing more granular control over performance optimization. UsePeerToPeerDataTransfer 参数现在可以在 Vertica 的子集群级别设置。此增强允许用户减少点对点（P2P）数据传输的开销，而无需在数据库级别禁用该功能，提供了更细粒度的性能优化控制。 |
| 4521827 | Third Party Tools Integration | Upgrade npm to secure version to address CVE-2024-47531. 升级 npm 到安全版本以修复 CVE-2024-47531。 |
| 4527291 | Security | The rsync connection for Linux file systems has been upgraded from version 3.2.7 to version 3.4.0 to fix these security vulnerabilities: 1. CVE-2024-12084 (https://nvd.nist.gov/vuln/detail/CVE-2024-12085) 2. CVE-2024-12085 (https://nvd.nist.gov/vuln/detail/CVE-2024-12084) Linux 文件系统的 rsync 连接已从 3.2.7 版本升级到 3.4.0 版本以修复安全漏洞：CVE-2024-12084 和 CVE-2024-12085。 |