25.4.x Resolved issues¶
25.4.0-6¶
Updated 04/29/2026
| Issue Key | Application Module | Description |
|---|---|---|
| 5333349 | Backup/DR | This update significantly improves the performance of the load_snapshot() operation. Previously, this process could take up to 4 hours on some nodes due to redundant checks. We have optimized the system to reduce repeated storage location verifications and introduced efficiencies in CRC checks, resulting in a faster and more streamlined snapshot loading experience.此更新显著提升了 load_snapshot() 操作的性能。此前，由于冗余检查，该过程在某些节点上可能耗时长达 4 小时。我们优化了系统以减少重复的存储位置验证，并引入了 CRC 检查的效率改进，从而实现了更快、更精简的快照加载体验。 |
| 5333790 | 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.4.0-5¶
Updated 04/10/2026
| Issue Key | Application Module | Description |
|---|---|---|
| 5196645 | 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 版本新增了一项优化，在兼容的情况下保留哈希/合并右外连接的外表排序。在此工单中，我们发现合并连接中该优化可能导致排序违规（在本例中会在使用聚合函数时产生不一致的结果）。为保持排序，我们在处理合并连接时恢复了显式排序路径。 |
| 5202820 | Kafka Integration | Core Vulnerability (CVE-2025-68161): 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.核心漏洞（CVE-2025-68161）：此更新修复了在 container_minimal_arm 环境 Prisma 扫描中发现的 org.apache.logging.log4j_log4j-core 版本 2.17.1 中的严重安全漏洞 CVE-2025-68161。Log4j 核心库已升级至 2.25.3 版本以缓解此问题。 |
| 5215118 | 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 读取可靠性。 |
| 5222638 | 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 语句值时的限制一致。 |
| 5223737 | Optimizer | Fixed an issue where complex queries involving Common Table Expressions (CTEs) and UNION operations could intermittently trigger an 'Internal Optimizer Error (11)'. This resolution ensures these queries now execute successfully without the need for workarounds such as adjusting the EnableWITHTempRelReuseLimit parameter. 修复了涉及公用表表达式（CTE）和 UNION 操作的复杂查询可能间歇性触发「内部优化器错误（11）」的问题。此修复确保这些查询现在可以成功执行，无需调整 EnableWITHTempRelReuseLimit 参数等临时解决方案。 |
| 5228322 | 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 容器镜像的安全性并确保集成和部署的合规性。 |
| 5249095 | 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 在处理投影时可能遇到内部类型不匹配，导致优化器断言失败。此问题已解决。 |
| 5256914 | Execution Engine | Resolved an issue where the database would crash (SIGSEGV panic) when executing queries involving the ~ ANY (Subquery) operator. This fix prevents unexpected server shutdowns and ensures continuous database accessibility.解决了执行涉及 ~ ANY (Subquery) 运算符的查询时数据库崩溃（SIGSEGV 恐慌）的问题。此修复防止了意外的服务器关闭，确保数据库持续可用。 |
| 5266216 | Optimizer | In some cases, union sub-queries with coercion could result in type conflicts and an internal error. This issue has been resolved. 在某些情况下，包含类型转换的 union 子查询可能导致类型冲突和内部错误。此问题已解决。 |
| 5291016 | Data load / COPY | FCSVPARSER used to incorrectly parse CRLF record terminators, leading in some cases to reject the data value of the last field in the record. Now, CRLF record terminators are properly parsed. FCSVPARSER 此前错误地解析 CRLF 记录终止符，在某些情况下导致拒绝记录中最后一个字段的数据值。现在，CRLF 记录终止符已被正确解析。 |
| 5297493 | Admin Tools | This release addresses critical and high-severity security vulnerabilities identified following the upgrade to version 23.4.0-23. This update resolves multiple Common Vulnerabilities and Exposures (CVEs), including CVE-2025-68121 (Critical) and several high-severity CVEs such as CVE-2024-37298, CVE-2025-61726, and others, enhancing the overall security posture of the system. 此版本解决了升级到 23.4.0-23 后发现的严重和高危安全漏洞。此更新修复了多个常见漏洞和暴露（CVE），包括 CVE-2025-68121（严重）和多个高危 CVE，如 CVE-2024-37298、CVE-2025-61726 等，提升了系统的整体安全性。 |
| 5297687 | EON | A new internal knob called RemoveBadRestorePointsOnStartup is added to allow progress of startup in the presence of bad restore points if enabled. 新增一个名为 RemoveBadRestorePointsOnStartup 的内部开关，启用后允许在存在损坏恢复点时继续启动进程。 |
25.4.0-4¶
Updated 03/03/2026
| Issue Key | Application Module | Description |
|---|---|---|
| 5109479 | 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 中，重新分片功能在所有扫描中都添加了分段列跟踪，即使不需要时也是如此——修复方案是仅在查询或重新分片场景特别需要时才跟踪分段列。 |
| 5177724 | 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 数据和超长字符串，从而恢复数据完整性并消除影响性能的临时解决方案。 |
| 5186169 | 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, ensuring the getting the correct and up-to-date catalog information.在此版本之前，AdminTools 的 restart_node 可能选择辅助 UP 节点来运行目录编辑器以获取目录信息。此修复后，AdminTools 的 restart_node 始终选择主 UP 节点来运行目录编辑器以获取目录信息，确保获取正确且最新的目录信息。 |
| 5200348 | Installation Program | --ssh-password Option Failure in install_vertica and update_vertica: Previously, the --ssh-password option in the install_vertica and update_vertica scripts was not being correctly applied. This led to the scripts prompting for an SSH password and becoming unresponsive during installation or upgrade processes, especially in environments where passwordless SSH was not configured. This behavior resulted in incomplete upgrades and operational disruptions. Resolution: The --ssh-password option is now properly recognized. The install_vertica and update_vertica scripts now correctly utilize the provided SSH password, ensuring smooth and uninterrupted execution without unexpected password prompts.install_vertica 和 update_vertica 中的 --ssh-password 选项失败：此前，install_vertica 和 update_vertica 脚本中的 --ssh-password 选项未被正确应用，导致脚本在安装或升级过程中提示输入 SSH 密码并变得无响应，特别是在未配置免密 SSH 的环境中。此行为导致升级不完整和运营中断。修复方案：--ssh-password 选项现在已被正确识别。install_vertica 和 update_vertica 脚本现在能正确使用提供的 SSH 密码，确保顺利无中断的执行，无需意外的密码提示。 |
| 5200955 | 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 数据中的第一个字符。 |
| 5206359 | 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 所指定的最长时间。 |
| 5222294 | Kubernetes, Vcluster | Before the fix, the Kubernetes operator may error out upon seeing remote user storage location when reviving an Eon database migrated from 10.x Enterprise database. With the fix, the Kubernetes operator correctly handles the remote user storage locations created in an older version enterprise database for reviving. 修复前，Kubernetes operator 在恢复从 10.x Enterprise 数据库迁移的 Eon 数据库时，遇到远程用户存储位置可能会报错。修复后，Kubernetes operator 能正确处理旧版本 Enterprise 数据库中创建的远程用户存储位置以进行恢复。 |
| 5225214 | AMI | Queries failing due to network errors in EE's Data Target Proxy are now retryable, allowing Vertica server to mitigate such failures with its retry mechanism. 由于 EE 的 Data Target Proxy 中网络错误而失败的查询现在支持重试，允许 Vertica 服务器通过其重试机制缓解此类故障。 |
25.4.0-3¶
Updated 1/27/2026
| Issue Key | Application Module | Description |
|---|---|---|
| 5108307 | Optimizer | Internal Optimizer Error during Complex View Updates: This release addresses an issue where UPDATE statements in Vertica would intermittently fail with an "Internal Optimizer Error". This error specifically occurred when the update statement involved joining with complex view structures, particularly when these views were defined across multiple schemas and referenced underlying tables in different schemas. This fix resolves the underlying optimizer issue and users can now perform these update operations reliably. 复杂视图更新时的内部优化器错误：此版本解决了 Vertica 中 UPDATE 语句间歇性失败并报「内部优化器错误」的问题。此错误特别发生在更新语句涉及与复杂视图结构连接时，尤其是当这些视图跨多个 Schema 定义并引用不同 Schema 中的基础表时。此修复解决了底层的优化器问题，用户现在可以可靠地执行这些更新操作。 |
25.4.0-2¶
Updated 1/21/2026
| Issue Key | Application Module | Description |
|---|---|---|
| 5080224 | Execution Engine | Replicated tables could error out when performing cross namespace ILM operations. This issue has been resolved. 复制表在执行跨命名空间 ILM 操作时曾出现错误。此问题已解决。 |
| 5080746 | Vcluster | The vcluster CLI has been updated to properly handle SIGINT (CTRL-C) signals. Previously, interrupting a vcluster command with CTRL-C would cause the terminal cursor to disappear, requiring a 'reset' or 'clear' command to restore it. This fix ensures that the cursor is reset to normal upon exiting vcluster with CTRL-C, preventing terminal display issues. Vcluster CLI 已更新以正确处理 SIGINT（CTRL-C）信号。此前，使用 CTRL-C 中断 vcluster 命令会导致终端光标消失，需要执行 reset 或 clear 命令恢复。此修复确保使用 CTRL-C 退出 vcluster 时光标恢复正常，防止终端显示问题。 |
| 5082884 | Security, Third Party Tools Integration | Security Update for Vertica Server and Operator: This release provides crucial security enhancements for the Vertica server and Vertica operator. It addresses multiple high and critical severity vulnerabilities, including CVE-2025-4517, CVE-2024-12254, and others, significantly improving the overall security posture of your Vertica environment. Vertica 服务器和 Operator 的安全更新：此版本为 Vertica 服务器和 Vertica operator 提供了关键安全增强。它解决了多个高危和严重漏洞，包括 CVE-2025-4517、CVE-2024-12254 等，显著提升了 Vertica 环境的整体安全性。 |
| 5092598 | Backup/DR | Int-String comparison in table expression used to fail VBR and VBR5 restore. This issue has been resolved. 表表达式中的整数字符串比较曾导致 VBR 和 VBR5 恢复失败。此问题已解决。 |
| 5139019 | Optimizer | Previously, enabling distributed SIPS resulted in some queries producing truncated results- not all expected rows were returned. This has been disabled until a root cause is known and fixed. 此前，启用分布式 SIPS 导致某些查询返回截断的结果——未返回所有预期的行。此功能已被禁用，直至找到根本原因并修复。 |
25.4.0-1¶
Updated 12/4/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 4939194 | UDX | Python UDx Installation Fix: Resolved an issue where users were unable to install Python User-Defined Extensions (UDx). This problem occurred when creating UDx libraries with large dependencies (such as torch) or when dependency paths contained special characters like '+', leading to a 'timed out in receiving a UDx message' error. This fix ensures successful Python UDx library creation under these conditions. Python UDx 安装修复：解决了用户无法安装 Python 用户自定义扩展（UDx）的问题。此问题发生在创建具有大型依赖项（如 torch）的 UDx 库时，或依赖路径包含特殊字符（如 '+'）时，导致「接收 UDx 消息超时」错误。此修复确保在这些条件下也能成功创建 Python UDx 库。 |
| 4945235 | Backup/DR | Object-Level Restore: Resolved an issue where object-level restores of tables using the RESTORE FROM ARCHIVE command could fail, often reporting a "can't find the folder in the node path" error. 对象级恢复：解决了使用 RESTORE FROM ARCHIVE 命令对表进行对象级恢复时可能失败的问题，通常报错「在节点路径中找不到文件夹」。 |
| 5008268 | Optimizer | Resolved Critical Database Crashes with LIKE ANY Clause: This release addresses a critical issue (Defect ID: 5008268) that caused Vertica databases to crash unexpectedly. The crash occurred when specific SQL queries utilized the LIKE ANY clause with an explicit cast to ARRAY[Varchar] (e.g., LIKE ANY ('%pattern%'::ARRAY[Varchar])). This fix enhances database stability and prevents service interruptions caused by such queries. 解决了 LIKE ANY 子句导致的关键数据库崩溃：此版本解决了一个关键问题（缺陷 ID：5008268），该问题导致 Vertica 数据库意外崩溃。当特定 SQL 查询使用带有显式转换为 ARRAY[Varchar] 的 LIKE ANY 子句时（例如 LIKE ANY ('%pattern%'::ARRAY[Varchar])），会发生崩溃。此修复增强了数据库稳定性，防止由此类查询引起的服务中断。 |
| 5013296 | 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 客户端认证才能使用 OAuth2 令牌登录，不会自动执行授权。伪超级用户始终按照 OAuth2JITConflictPolicy 设置为 IGNORE 处理，即他们只能使用已显式授予的认证方法。 |
| 5019107 | 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（Unicode 国际组件）库进行字符串比较。虽然 ICU 为复杂的区域感知比较提供了 robust 支持，但这种转换引入了开销，特别是对于简单用例。现在，对于具有 1 对 1 字符映射的简单区域（如 en_US、de_DE 等每个字符在 UTF-8 和 UTF-16 之间直接映射而无需规范化或多码点处理的区域），STRPOS 使用基于 UTF-8 的比较，避免了转换为 UTF-16 并完全绕过了 ICU 库，从而实现更快的执行速度。 |
| 5041757 | Admin Tools | fjsonparser incompatibility issue: This fix ensures the upgrade process is successful and correctly handles the FlexTableLib library, resolving the fjsonparser incompatibility issue. fjsonparser 不兼容问题：此修复确保升级过程成功并正确处理 FlexTableLib 库，解决了 fjsonparser 不兼容的问题。 |
| 5043725 | License | An issue was found, where the audit functionality was producing invalid results, leading to inaccurate size reporting. This issue has been fixed to ensure the audit size accurately reflects the actual data size. 发现审计功能产生无效结果，导致大小报告不准确的问题。此问题已修复，确保审计大小准确反映实际数据大小。 |
| 5057904 | EON | Crashes Due to OOM Errors: 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 错误导致的崩溃：此版本解决了集群节点因内存不足（OOM）错误频繁崩溃的问题。此问题在主从子集群中均有观察到，RSS 内存使用持续增长，即使空闲的从子集群也是如此。此修复解决了影响所有主机的内存泄漏问题，无论硬件规格或操作系统如何。 |
| 5085485 | Data Networking | Database Hanging After Upgrade: Addressed a high-severity issue where Vertica databases could experience hangs shortly after upgrading to version 25.3.0-2. This issue was particularly observed when TLS 1.3 was enabled (MinTLSVersion = 3). This resolution improves database stability and prevents unexpected unresponsiveness post-upgrade. 升级后数据库挂起：解决了一个高危问题，即 Vertica 数据库在升级到 25.3.0-2 后不久可能发生挂起。当启用 TLS 1.3（MinTLSVersion = 3）时尤其容易发生。此修复提升了数据库稳定性，防止升级后出现意外的无响应情况。 |
| 5086370 | Data Networking | Improved System Stability: TS Callback Deadlock ResolutionResolved a potential deadlock (ID: 5086370) that could occur when TS callback destructors executed while holding a lock. This fix prevents conflicts, especially with the async Messenger notifier, enhancing overall system reliability. 系统稳定性改进：TS 回调死锁解决 - 解决了 TS 回调析构函数在持有锁时执行可能导致死锁的问题（ID：5086370）。此修复防止了冲突，特别是与异步 Messenger 通知器的冲突，增强了整体系统可靠性。 |
25.4.0-0¶
Updated 10/20/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 4536473 | WLA - Workload Analyzer | Fixed an issue where "no histogram" messages were incorrectly displayed in dc_optimizer_events for Live Aggregate Projection (LAP) projections with statistics. This issue affected workload analyzer accuracy. The fix ensures that histogram information is correctly reported for LAP projections, providing accurate data for workload analysis. 修复了在具有统计信息的实时聚合投影（LAP）投影的 dc_optimizer_events 中错误显示「无直方图」消息的问题。此问题影响了工作负载分析器的准确性。修复确保为 LAP 投影正确报告直方图信息，为工作负载分析提供准确数据。 |
| 4344413 | Security | Fixed an issue where creating access policies added extra parentheses, causing COPY_TABLE to fail with an access policy mismatch error. 修复了创建访问策略时添加了额外括号，导致 COPY_TABLE 因访问策略不匹配错误而失败的问题。 |
| 4350082 | Monitoring, UI Management Console | Fixed an issue where SNMP trap events and system log event settings were not being applied correctly in Management Console 24.x. Users can now successfully configure and save these settings. 修复了 Management Console 24.x 中 SNMP 陷阱事件和系统日志事件设置未正确应用的问题。用户现在可以成功配置和保存这些设置。 |
| 4392317 | Security | Fixed an issue where Vertica's OAuth2 authentication method incorrectly handled EC keys. The system now accurately supports RSA keys for JWT validation, resolving the 'failed to load public key' error encountered when using EC keys. This enhancement ensures seamless integration with Keycloak IDP and other identity providers using RSA-signed JWT tokens. 修复了 Vertica 的 OAuth2 认证方法错误处理 EC 密钥的问题。系统现在准确支持 RSA 密钥进行 JWT 验证，解决了使用 EC 密钥时遇到的「加载公钥失败」错误。此增强确保与 Keycloak IDP 及其他使用 RSA 签名 JWT 令牌的身份提供者的无缝集成。 |
| 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). 在 Vertica 数据库（RPM 和容器）附带的 Go 二进制文件（vcluster、vcluster_server 和 node_management_agent）中发现了关键安全漏洞并已修复。 |
| 4771462 | UI - Management Console | The Vertica Management Console (MC) version 25.1.0-0 does not allow users to control the number of EBS volumes provisioned during the revive Eon Mode Database process. This fix ensures that users can specify the desired number of EBS volumes, addressing the issue where the total volume size was not being divided as expected. This enhancement provides users with greater flexibility and control over their EBS volume configuration. Vertica Management Console（MC）25.1.0-0 版本不允许用户在恢复 Eon 模式数据库过程中控制预置的 EBS 卷数量。此修复确保用户可以指定所需的 EBS 卷数量，解决了总卷大小未按预期分配的问题。此增强为用户提供了更大的 EBS 卷配置灵活性和控制力。 |
| 4824434, 4862238 | UI - Management Console | Fixed an issue where N2 series machines were not visible in the MC provisioning tool for the us-east4-c region on GCP, despite their availability in the GCP console. This fix enables users to provision N2 series machines through MC in the specified region. Note that while N2 support has been added, N4 machine types are not supported by MC for Vertica. 修复了在 GCP 的 us-east4-c 区域中，N2 系列机器在 MC 配置工具中不可见的问题，尽管它们在 GCP 控制台中可用。此修复允许用户通过 MC 在指定区域配置 N2 系列机器。注意：虽然已添加 N2 支持，但 MC 不支持 N4 机器类型用于 Vertica。 |
| 4846116 | Third Party Tools | Fixed a critical security vulnerability (CVE-2024-45337) in the Vertica Docker image (opentext/vertica-k8s:24.4.0-1). 修复了 Vertica Docker 镜像（opentext/vertica-k8s:24.4.0-1）中的关键安全漏洞（CVE-2024-45337）。 |
| 4854920 | UI - Management Console | Fixed an issue in the Management Console (MC) where SMTP configuration without authentication was not supported. Restored the original email functionality by allowing SMTP configurations that do not require a username and password, as per product documentation. 修复了 Management Console（MC）中 SMTP 配置不支持无认证方式的问题。通过允许不需要用户名和密码的 SMTP 配置（符合产品文档），恢复了原有的电子邮件功能。 |
| 4858078 | Security | Fixed a bug where dropping a role assigned via OAuth JIT user provisioning and then attempting to authenticate the user after the role is dropped would cause an internal error. This error no longer occurs. 修复了一个错误：删除通过 OAuth JIT 用户预配置分配的角色，然后尝试在该角色被删除后认证用户会导致内部错误。此错误已不再发生。 |
| 4860823 | 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 子查询时出现。此问题已解决。 |
| 4861828 | Optimizer | Fixed an issue where INSERT…SELECT statements would hang when GROUPBY PUSHDOWN was not occurring due to the presence of non-equi joins. 修复了由于非等值连接导致 GROUPBY PUSHDOWN 未发生时，INSERT...SELECT 语句挂起的问题。 |
| 4866130 | Hadoop, Resource Manager | After upgrading from version 12.0.4 to 25.1, the Vertica Database failed to start due to a timeout issue, resulting in a core dump during the 'Read DataCollector' stage. A fix has been implemented to resolve this startup failure. 从 12.0.4 升级到 25.1 后，Vertica 数据库因超时问题无法启动，在「Read DataCollector」阶段产生核心转储。已实施修复以解决此启动失败问题。 |
| 4882688 | QA - MC | A fix has been implemented to address an issue where MC extended monitoring was not streaming data in Vertica Management Console. The fix ensures that data is correctly displayed in the MC. 已实施修复以解决 MC 扩展监控未在 Vertica Management Console 中流式传输数据的问题。修复确保数据在 MC 中正确显示。 |
| 4898183 | 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 模式集群之间的基于服务器的复制失败的问题。复制现在可在迁移后的集群和新安装的集群之间正常运行。 |
| 4920734 | Data load / COPY | Fixed a use-after-free issue that caused Vertica node crashes when loading large JSON data. The issue occurred during the destruction of an ArrayWriter when an error was raised due to insufficient UDLMaxDataBufferSize. The fix ensures that memory is properly managed during error conditions, preventing the crash. 修复了加载大型 JSON 数据时由于 use-after-free 问题导致 Vertica 节点崩溃的问题。此问题发生在因 UDLMaxDataBufferSize 不足而引发错误时 ArrayWriter 的销毁过程中。修复确保在错误条件下正确管理内存，防止崩溃。 |
| 4935630 | Data load / COPY | When enabling knob CopyFaultTolerantExpressions, COPY commands with ill-formed column expressions used to core dump. Now, Vertica returns a proper error message about the faulty expression. 启用 CopyFaultTolerantExpressions 参数后，包含格式错误的列表达式的 COPY 命令此前会导致核心转储。现在，Vertica 会返回关于错误表达式的适当错误消息。 |
| 4936293 | SDK - Python | Resolved an issue where the 'ssl' module lacked the 'wrap_socket' attribute due to its deprecation in Python 3.12. The vertica-python library has been upgraded to a compatible version that utilizes 'ssl.create_default_context()' instead, resolving the error and ensuring compatibility with newer Python versions. 解决了 ssl 模块因 Python 3.12 中弃用而缺少 wrap_socket 属性的问题。vertica-python 库已升级到使用 ssl.create_default_context() 的兼容版本，解决了该错误并确保与更新版本 Python 的兼容性。 |
| 4948330 | Cloud - Amazon | The cluster was experiencing "Cluster Truncation Lag" due to nodes encountering "ExpiredToken" errors when reading from Parquet files in S3. This issue was causing the catalog truncation version to lag, requiring node restarts to resolve. A fix has been implemented to ensure the SDK correctly handles token expiration and retries, preventing the "ExpiredToken" errors and subsequent catalog synchronization issues. 集群因节点在从 S3 读取 Parquet 文件时遇到「ExpiredToken」错误而出现「集群截断滞后」问题。此问题导致目录截断版本滞后，需要重启节点才能解决。已实施修复以确保 SDK 正确处理令牌过期和重试，防止「ExpiredToken」错误及后续的目录同步问题。 |
| 4948707 | Execution Engine | A node crash was triggered by a VAssert failure related to memory allocation within the Vertica database, specifically the assertion VAssert(toCheckCleared[0] == 0 && (memSize < 16 || toCheckCleared[1] == 0)) failed. This issue has been addressed, preventing further node crashes related to this memory allocation assertion. 与 Vertica 数据库内部分配相关的 VAssert 失败（具体为 VAssert(toCheckCleared[0] == 0 && (memSize < 16 |
| 4951289 | UI - Management Console | Resolved security vulnerabilities related to Tomcat and Spring Security. Updated Apache Tomcat to version 10.1.42 and Spring Security to version 6.4.4 to address CVE-2024-50379, CVE-2024-54677, CVE-2024-56337, CVE-2025-24813, CVE-2025-31650, CVE-2025-31651, CVE-2025-46701, CVE-2025-48976, CVE-2025-48988, CVE-2025-49124, CVE-2025-49125 and CVE-2025-22228. 解决了与 Tomcat 和 Spring Security 相关的安全漏洞。Apache Tomcat 已更新至 10.1.42，Spring Security 已更新至 6.4.4，以解决 CVE-2024-50379、CVE-2024-54677、CVE-2025-24813、CVE-2025-31650、CVE-2025-31651、CVE-2025-46701、CVE-2025-48976、CVE-2025-48988、CVE-2025-49124、CVE-2025-49125 和 CVE-2025-22228。 |
| 4971271 | Hadoop, UDX | Addressed a critical security vulnerability, CVE-2022-23305 (CWE-89), identified through SBOM scanning of Vertica server, console, and JDBC client packages. This vulnerability could potentially block customer installations. This release resolves the vulnerability to ensure secure deployments. 解决了通过 Vertica 服务器、控制台和 JDBC 客户端包的 SBOM 扫描发现的严重安全漏洞 CVE-2022-23305。此漏洞可能阻止客户安装。此版本修复了该漏洞以确保安全部署。 |
| 5015913 | Kubernetes | Operator version 25.3.0-0 contains critical vulnerability CVE-2025-22871 and high-severity vulnerability CVE-2025-47907 in stdlib v1.23.5. To get the operator fix, please upgrade to the new version. Operator 版本 25.3.0-0 包含 stdlib v1.23.5 中的严重漏洞 CVE-2025-22871 和高危漏洞 CVE-2025-47907。如需获取 operator 修复，请升级到新版本。 |