25.3.x Resolved issues¶
25.3.0-10¶
Updated 6/3/2026
| Issue Key | Application Module | Description |
|---|---|---|
| 5159223 | Execution Engine | Vertica was not 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 之前无法处理数组中含有用户自定义函数的查询。现在已能按预期处理此情况，最坏情况下也不会崩溃。 |
| 5289143 | Optimizer | Overly restrictive error handling was added for complex/nested complex types containing user-defined functions. This was causing some valid SQL to report an 'unsupported' error when it should not have. This has been fixed. 对包含用户自定义函数的复杂/嵌套复杂类型添加了过于严格的错误处理，导致部分合法 SQL 误报「不支持」错误。此问题已修复。 |
| 5332449 | Execution Engine | Previously, float division evaluation would produce an INFO line of log output to note the inputs and outputs of the operation. This output was extraneous and caused rapid log file growth that scaled linearly with the number of rows processed for certain queries. Now this log output has been removed. 此前浮点除法运算会产生 INFO 级别日志输出记录操作输入输出，对于某些查询日志量随处理行数线性增长，导致日志文件快速膨胀。此日志输出现已移除。 |
| 5347454 | Optimizer | Certain combinations of expressions, sublinks, and group by used in a single query could result in an internal error; this has been resolved. 在单个查询中同时使用特定的表达式、子链接和 GROUP BY 组合可能导致内部错误；此问题已解决。 |
| 5381293 | UI - Management Console | This update addresses a critical security vulnerability, CVE-2025-12453, identified as a Reflected Cross-Site Scripting (XSS) flaw in Vertica, specifically affecting version 10.0.1. Prior to this fix, an authenticated attacker could exploit unmanaged input parameters in certain Web UI endpoints to inject and execute arbitrary JavaScript code. This update includes essential security enhancements to mitigate the identified XSS vulnerability and measures to ensure proper sanitization and neutralization of user-supplied input, preventing the execution of malicious scripts. Users are advised to update to the latest version to benefit from these security improvements. 此更新修复了一个严重安全漏洞 CVE-2025-12453，该漏洞为 Vertica 中的反射型跨站脚本（XSS）缺陷，影响版本 10.0.1。此前，已认证攻击者可利用某些 Web UI 端点中未受管理的输入参数注入并执行任意 JavaScript 代码。此更新包含关键安全增强措施以缓解该 XSS 漏洞，并确保对用户输入进行适当的清理和中性化处理，防止恶意脚本执行。建议用户更新至最新版本以获得这些安全改进。 |
| 5386128 | Security | This update addresses a critical security vulnerability, identified as CVE-2026-33186, that was discovered within the gRPC dependency utilized by the Vertica database server. 此更新修复了一个严重安全漏洞 CVE-2026-33186，该漏洞存在于 Vertica 数据库服务器所使用的 gRPC 依赖库中。 |
25.3.0-9¶
Updated 04/28/2026
| Issue Key | Application Module | Description |
|---|---|---|
| 5222708 | Optimizer | This release addresses an 'Internal Optimizer Error (11)' that could occur when executing specific complex SQL queries involving Common Table Expressions (CTEs) and UNION operations. Previously, this error necessitated a workaround by adjusting the EnableWITHTempRelReuseLimit parameter. With this fix, affected queries will now execute successfully without optimizer failures, enhancing query reliability and eliminating the need for the previous workaround.此版本解决了执行涉及公用表表达式（CTE）和 UNION 操作的特定复杂 SQL 查询时可能出现的「内部优化器错误（11）」。此前，此错误需要调整 EnableWITHTempRelReuseLimit 参数作为临时解决方案。此修复后，受影响的查询将成功执行而不会出现优化器故障，提高了查询可靠性并无需之前的临时解决方案。 |
| 5256913 | 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) 查询时的稳定性和防止数据库恐慌。 |
| 5270220 | Optimizer | In some cases, union sub-queries with coercion could result in type conflicts and an internal error. This issue has been resolved. 在某些情况下，包含类型转换的 union 子查询可能导致类型冲突和内部错误。此问题已解决。 |
| 5297494 | Admin Tools | This update addresses multiple critical and high-severity security vulnerabilities that were identified following an upgrade to version 23.4.0-23. These fixes significantly enhance the overall security posture of the system. Note: Users are strongly encouraged to apply this update to ensure their systems are protected against these identified security risks. 此更新解决了升级到 23.4.0-23 后发现的多个严重和高危安全漏洞。这些修复显著提升了系统的整体安全性。注意：强烈建议用户应用此更新以确保系统免受这些已识别安全风险的影响。 |
| 5297688 | EON | A new internal knob called RemoveBadRestorePointsOnStartup is added to allow progress of startup in the presence of bad restore points, if enabled.新增一个名为 RemoveBadRestorePointsOnStartup 的内部开关，启用后允许在存在损坏恢复点时继续启动进程。 |
| 5330988 | Backup/DR | Performance Improvement for Snapshot Loading: This release addresses a performance bottleneck observed during the load_snapshot() operation, which could sometimes take up to 4 hours on certain nodes. Key Improvements: - Optimized Storage Container Checks: Reduced redundant checks for storage locations within Storage Containers (SCs). - Streamlined CRC Verification: Introduced optimizations to skip unnecessary CRC checks for existing storage bundles. These enhancements significantly improve the efficiency and reduce the duration of the load_snapshot() process, leading to faster system recovery and improved overall performance.快照加载性能改进：此版本解决了 load_snapshot() 操作中观察到的性能瓶颈，该操作在某些节点上可能耗时长达 4 小时。关键改进：优化了存储容器（SC）内的存储位置检查，减少了冗余检查；简化了 CRC 验证，引入优化以跳过对现有存储 bundle 的不必要 CRC 检查。这些增强显著提高了 load_snapshot() 过程的效率和减少耗时，从而实现更快的系统恢复和改进的整体性能。 |
| 5335639 | 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.3.0-8¶
Updated 03/09/2026
| Issue Key | Application Module | Description |
|---|---|---|
| 5196646 | Execution Engine | Fix for Inconsistent CASE Statement Evaluation in SQL Queries: An enhancement was added in version 24.1 which aimed to preserve the outer relation in hash/merge right outer joins. However, this enhancement was found to inadvertently cause sort violations in specific merge join scenarios. These sort violations could lead to inconsistent results, especially when aggregate functions were used in conjunction with CASE statements, causing the same logical record to yield different evaluated values (e.g., 'None' versus 'Ref-53' for an exclusion_rule_ref column). Resolution: To resolve this, an explicit Sort path has been reinstated for merge joins. This ensures that the correct sort order is consistently maintained during query execution, thereby preventing sort violations and guaranteeing that CASE statement evaluations and aggregate functions return accurate and consistent values as expected.修复 SQL 查询中 CASE 语句评估不一致的问题：24.1 版本新增了一项优化，旨在保留哈希/合并右外连接中的外表。然而，此优化在某些合并连接场景中意外导致排序违规。这些排序违规可能导致不一致的结果，特别是当聚合函数与 CASE 语句一起使用时，导致同一逻辑记录产生不同的评估值（例如，exclusion_rule_ref 列显示「None」而非「Ref-53」）。解决方案：为恢复正确的排序，已为合并连接重新引入显式排序路径。这确保在查询执行过程中一致地维护正确的排序顺序，从而防止排序违规，并保证 CASE 语句评估和聚合函数按预期返回准确一致的值。 |
| 5174220, 5202821 | 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 版本以缓解此问题。 |
| 5209664 | S3X | S3 Streaming Connection Handling Improved: 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 请求激增时可能导致连接池耗尽。这会阻塞 S3 读取操作和查询，包括 TxnLogSync 等关键服务。此修复确保流式连接被正确计数并强制执行限制，防止连接枯竭并提高 S3 读取可靠性。 |
| 5224615 | 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 语句值时的限制一致。 |
| 5245093 | 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 在处理投影时可能遇到内部类型不匹配，导致优化器断言失败。此问题已解决。 |
25.3.0-7¶
Updated 03/03/2026
| Issue Key | Application Module | Description |
|---|---|---|
| 4937245 | QA - MC | A fix has been implemented to address an issue where Vertica Management Console (MC) extended monitoring was not streaming data in the MC. The fix ensures that data is correctly displayed in the MC. 已实施修复以解决 Vertica Management Console（MC）扩展监控未在 MC 中流式传输数据的问题。修复确保数据在 MC 中正确显示。 |
| 5109097 | Optimizer | Internal Optimizer Error with Complex View Joins: 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）」的问题。涉及这些复杂视图结构的更新查询现在可按预期正常执行。 |
| 5139018 | 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 导致某些查询返回截断的结果——未返回所有预期的行。此功能已被禁用，直至找到根本原因并修复。 |
| 5180139 | 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 数据和超长字符串，从而恢复数据完整性并消除影响性能的临时解决方案。 |
| 5184560 | 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 节点来运行目录编辑器以获取目录信息，确保获取正确且最新的目录信息。 |
| 5197757 | 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 密码，确保顺利无中断的执行。 |
| 5203361 | 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 数据中的第一个字符。 |
| 5203794 | 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 所指定的最长时间。 |
| 5223278 | Kubernetes, Vcluster | Before the fix, Kubernetes operator may error out upon seeing remote user storage location when reviving an Eon database migrated from 10.x Enterprise database. Now, Kubernetes operator correctly handles the remote user storage locations created in old version enterprise database for reviving. 修复前，Kubernetes operator 在恢复从 10.x Enterprise 数据库迁移的 Eon 数据库时，遇到远程用户存储位置可能会报错。现在，Kubernetes operator 能正确处理旧版本 Enterprise 数据库中创建的远程用户存储位置以进行恢复。 |
| 5224193 | 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.3.0-6¶
Updated 01/29/2026
| Issue Key | Application Module | Description |
|---|---|---|
| 5014761 | Admin Tools | Corrected logrotate Help Output: Previously, running admintools -t logrotate --help displayed an incorrect usage message, showing Usage: logrotateconfig [options]. This was misleading as logrotateconfig is not a valid tool name. Now, the help output for admintools -t logrotate --help has been corrected to accurately display Usage: logrotate [options], along with the valid options list. This fix improves the accuracy of admintools help text and ensures consistency between the command-line interface and documentation.更正 logrotate 帮助输出：此前，运行 admintools -t logrotate --help 显示错误的使用信息，显示为 Usage: logrotateconfig [options]。这是误导性的，因为 logrotateconfig 不是有效的工具名称。现在，admintools -t logrotate --help 的帮助输出已更正为准确显示 Usage: logrotate [options] 以及有效选项列表。此修复改进了 admintools 帮助文本的准确性，确保命令行界面和文档之间的一致性。 |
| 5104466 | 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 配置参数，消除了每日的错误消息和误报。 |
| 5108700 | 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 中，重新分片功能在所有扫描中都添加了分段列跟踪，即使不需要时也是如此。修复方案是仅在查询或重新分片场景特别需要时才跟踪分段列。 |
| 5144015 | MC | 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）。 |
25.3.0-5¶
Updated 12/11/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 4989560 | 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 |
| 5078585 | Execution Engine | Replicated tables used to error out when performing cross namespace ILM operations. This issue has been resolved. 复制表在执行跨命名空间 ILM 操作时曾出现错误。此问题已解决。 |
| 5081095 | 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 时光标恢复正常，防止终端显示问题。 |
| 5084329 | Security, Third Party Tools Integration | A critical and high-severity vulnerability fix has been implemented for Vertica server and Vertica Operator. This addresses multiple CVEs, including CVE-2025-4517, CVE-2014-9114, CVE-2016-2779, CVE-2017-2616, CVE-2024-12254, CVE-2024-28085, CVE-2025-27516, CVE-2025-4138, CVE-2025-4330, CVE-2025-4435, CVE-2025-4674, and CVE-2025-8194, improving the security posture of the affected components. 已为 Vertica 服务器和 Vertica Operator 实施了严重和高危漏洞修复。这解决了多个 CVE，包括 CVE-2025-4517、CVE-2014-9114、CVE-2016-2779、CVE-2017-2616、CVE-2024-12254、CVE-2024-28085、CVE-2025-27516、CVE-2025-4138、CVE-2025-4330、CVE-2025-4435、CVE-2025-4674 和 CVE-2025-8194，改进了受影响组件的安全性。 |
| 5084590 | 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 模式集群之间的基于服务器的复制失败的问题。复制现在可在迁移后的集群和新安装的集群之间正常运行。 |
| 5085430 | Data Networking | TS callback dtor should cleanup without the lock Description: 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. Resolution: 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 回调析构函数应在无锁状态下清理：解决了 TS 回调析构函数在持有锁时执行可能导致死锁的问题。这可能与也可能需要同一锁的其他系统组件（如异步 Messenger 通知器）发生冲突。解决方案：系统已更新，确保 TS 回调析构函数在锁外执行，从而防止死锁并提高整体系统稳定性。 |
| 5087104 | Data Networking | Database Hung Issue After Vertica 25.3.0-2 Upgrade: 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 升级后的数据库挂起问题：已解决一个高危问题，即 Vertica 数据库在升级到 25.3.0-2 后不久会挂起，特别是在 MinTLSVersion 设置为 3 时。此修复包含在 25.3.0-5 版本中，确保数据库稳定性并防止所有节点上的 SQL 查询卡住，恢复正常操作。 |
| 5093599 | Backup/DR | Int-String comparison in table expression used to fail VBR and VBR5 restore. This issue has been resolved. 表表达式中的整数字符串比较曾导致 VBR 和 VBR5 恢复失败。此问题已解决。 |
25.3.0-4¶
Updated 11/18/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 5004897 | 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 内存使用持续增长，即使空闲的从子集群也是如此。此修复解决了影响所有主机的内存泄漏问题，无论硬件规格或操作系统如何。 |
| 5040783 | Admin Tools | This fix ensures the upgrade process is successful and correctly handles the FlexTableLib library, resolving the fjsonparser incompatibility issue. 此修复确保升级过程成功并正确处理 FlexTableLib 库，解决了 fjsonparser 不兼容的问题。 |
| 5045276 | Licenses | An issue was found, where the audit functionality was producing invalid results, leading to inaccurate size reporting. This issue has been resolved to ensure the audit size accurately reflects the actual data size. 发现审计功能产生无效结果，导致大小报告不准确的问题。此问题已解决，确保审计大小准确反映实际数据大小。 |
| 5048764 | License | 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.3.0-3¶
Updated 10/10/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 4880317 | System: Performance | A fix has been implemented that addresses the performance bottleneck associated with the STRPOS function in specific scenarios, as when used with GROUP BY on large datasets (millions of rows). 已实施修复，解决了特定场景下 STRPOS 函数的性能瓶颈问题，例如在大型数据集（数百万行）上与 GROUP BY 一起使用时。 |
| 4970327 | Security | Fixed an issue where creating access policies added extra parentheses, causing COPY_TABLE to fail with an access policy mismatch error. 修复了创建访问策略时添加了额外括号，导致 COPY_TABLE 因访问策略不匹配错误而失败的问题。 |
| 4988444 | 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 子查询时出现。此问题已解决。 |
| 5007482 | Client Drivers - JDBC | Resolved an issue where the JDBC driver was preventing connections to Vertica 25.3 clusters configured for TLS 1.3. The updated driver now fully supports TLS 1.3, ensuring secure and compliant connectivity. 解决了 JDBC 驱动阻止连接到配置了 TLS 1.3 的 Vertica 25.3 集群的问题。更新后的驱动现在完全支持 TLS 1.3，确保安全合规的连接。 |
| 5008269 | Optimizer | Resolved a critical issue that caused Vertica databases to crash when executing queries containing LIKE ANY with an explicit cast to ARRAY[Varchar] (e.g., LIKE ANY ('%value%'::ARRAY[Varchar])). This fix enhances database stability and prevents unexpected service interruptions. 解决了一个关键问题，即执行包含 LIKE ANY 并显式转换为 ARRAY[Varchar] 的查询时（例如 LIKE ANY ('%value%'::ARRAY[Varchar])）会导致 Vertica 数据库崩溃。此修复增强了数据库稳定性，防止意外服务中断。 |
| 5012268 | Security | 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 处理，即他们只能使用已显式授予的认证方法。 |
25.3.0-2¶
Updated 09/16/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 4930242 | Admin Tools | This release includes a fix for a critical issue encountered during upgrades from Vertica 24.3 to 25.3. The admin tools were reporting the database as 'down' due to a 'module 'ssl' has no attribute 'wrap_socket' error, caused by the deprecation of the wrap_socket function in newer Python versions used by admintools. 此版本包含修复从 Vertica 24.3 升级到 25.3 时遇到的关键问题。管理工具因「模块 ssl 没有 wrap_socket 属性」错误而报告数据库为「down」状态，这是由于 admintools 使用的较新 Python 版本中弃用了 wrap_socket 函数所致。 |
| 4958248 | Cloud - Amazon | Fixed an issue where Vertica nodes in Eon Mode clusters on AWS experience 'ExpiredToken' errors when reading from Parquet files in S3. This issue causes catalog truncation to lag, requiring node restarts. The fix ensures the SDK retries token retrieval after initial failures, preventing disruption to business operations. 修复了 AWS 上 Eon 模式集群中的 Vertica 节点在从 S3 读取 Parquet 文件时遇到「ExpiredToken」错误的问题。此问题导致目录截断滞后，需要重启节点。修复确保 SDK 在初始失败后重试令牌获取，防止对业务运营造成中断。 |
25.3.0-1¶
Updated 08/28/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 4883703 | Admin Tools | The Vertica Admin Tools was incorrectly displaying the database status as 'down' when TLS was enabled, even though the database was accessible via vSQL. This issue has been resolved. Admin Tools now accurately reflects the database status when TLS is enabled. Vertica Admin Tools 在启用 TLS 时错误地显示数据库状态为「down」，尽管数据库可通过 vSQL 访问。此问题已解决。Admin Tools 现在在启用 TLS 时准确反映数据库状态。 |
| 4960384 | SDK - Python | Fix: Upgraded vertica-python to resolve the 'ssl.wrap_socket' deprecation issue. The previous version (1.1.2) used 'ssl.wrap_socket()', which is deprecated in Python 3.12, causing errors. This update replaces the deprecated function with 'ssl.create_default_context()', ensuring compatibility with newer Python versions. 修复：升级 vertica-python 以解决 ssl.wrap_socket 弃用问题。先前版本（1.1.2）使用了 ssl.wrap_socket()，该函数在 Python 3.12 中已弃用，导致错误。此更新用 ssl.create_default_context() 替换了已弃用的函数，确保与较新 Python 版本的兼容性。 |
25.3.0-0¶
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. Vertica ODBC 驱动版本 12 已更新，解决了驱动错误引用 XML 错误消息文件内部路径的问题。 |
| 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. Vertica 12.0.2 之前版本中的 LISTAGG 函数在使用 WITHIN GROUP BY 子句时，其内存消耗显著高于不使用该子句的情况。此问题已解决。使用和不使用 WITHIN GROUP BY 子句时的内存消耗现已更加一致。 |
| 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. 从 Vertica 9.3 开始，包含特殊字符的文件名采用 UTF-8 格式。如果加载带有特殊字符文件名的文件时出现问题，请确保编码、代码页和区域设置已配置为支持 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. 在 Vertica v24.1 中，VSQL 选项 -v AUTOCOMMIT=ON 未能按预期工作。此版本解决了此问题，确保通过 VSQL 的 -v 选项指定时自动提交被正确启用。 |
| 4348576 | UI - Management Console | The issue where users were unable to configure resource pool alerts in the Management Console (MC) has been resolved. 解决了用户在 Management Console（MC）中无法配置资源池警报的问题。 |
| 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. 修复了导入的 TensorFlow 模型在预测期间需要意外数量的输入列（64 列而非 6 列）的问题。模型现在正确处理其元数据（tf_model_desc.json）和模型摘要中定义的预期 6 个输入特征。 |
| 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. 在 TM 活动期间，由于目录争用，某些查询的延迟可能增加。此问题已修复。 |
| 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. 用户无法在 Management Console（MC）24.x 版本中创建新的资源池警报。单击 Create Alert 按钮无响应，阻止了创建新的资源池警报。此问题现已解决。 |
| 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. 解决了 flex 数据大小估计中标准差计算的溢出问题。修复确保方差和标准差的准确计算，防止出现 NaN（非数字）值。 |
| 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. 表 error_messages 中经常包含描述类似「跳过节点信息，原因：未知 node_id」的警告消息条目。此消息并不表示真正的问题，因此已被移除。 |
| 4393228 | UI - Management Console | This release addresses MC vulnerabilities identified using the 'BlackDuck' tool. 此版本解决了使用 BlackDuck 工具识别的 MC 漏洞。 |
| 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. 在大型 JSON 文件的极端情况下，如果字符串字段中存在转义字符，解析后的字符串值可能缺少几个字符。此问题已解决。 |
| 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. 由于 librdkafka 断言失败，升级到 Vertica 25.1 后节点崩溃。此问题已解决。 |
| 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. 存在一个问题：即使 MEMORY_PUSHBACK 正在阻塞事务并导致应用程序错误，健康检查仍指示健康状态。此问题已解决。集群健康检查现在能可靠指示集群处理事务的能力，允许主动识别和解决内存压力问题。 |
| 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. 修复了升级到 Vertica v25.1 后，Kafka 调度程序在 FIPS 和非 FIPS 系统上创建失败的问题。 |
| 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. 已实施修复，解决了系统在提交操作期间因无法获取全局目录 X 锁（GCLX）而导致节点崩溃的问题，特别影响 insert 语句。 |
| 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. 解决了升级到 vertica-25.1.0 后，由致命信号 SIGSEGV 导致的 PANIC 触发的节点故障问题。修复包括对 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. ANTI_PIN 策略已更新，尽可能避免下载文件。此前，标记为 ANTI_PIN 的文件会被下载然后立即驱逐，这可能堵塞 fetcher 队列并消耗不必要的资源。 |
| 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. 解决了添加到表列的注释未在 jdbc_columns 表中更新的问题。此更新确保 jdbc_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. 解决了升级到 vertica-25.1.0 后，由致命信号 SIGSEGV 导致的 PANIC 触发的节点故障问题。修复包括对 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. 修复了 VerticaDB Operator 在使用 IPv6 的 Kubernetes 上遇到部署问题的问题。Operator 会陷入尝试重启 pod 的循环，错误地检测到 Vertica 未启动。 |
| 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）中发现了关键安全漏洞并已修复。 |
| 4725483 | Kubernetes | Fixed an issue where creating a Vertica restore point would fail when the database was created using initpolicy set to Revive. 修复了当数据库使用的 initpolicy 设置为 Revive 时，创建 Vertica 恢复点失败的问题。 |
| 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. - CVE-2024-42353: Upgrade WebOb to version 1.8.8 or higher. - CVE-2023-5752: Upgrade Mercurial to version 23.3 or higher. - CVE-2024-3651: Upgrade Inda package to version 3.7 or higher. 已解决 Vertica 随附的 Python 包中的以下安全漏洞：CVE-2024-39689：将 Certifi 升级到 2024.07.04 或更高版本；CVE-2024-42353：将 WebOb 升级到 1.8.8 或更高版本；CVE-2023-5752：将 Mercurial 升级到 23.3 或更高版本；CVE-2024-3651：将 Inda 包升级到 3.7 或更高版本。 |
| 47700789 | SDK-Python | This release includes a critical security update, upgrading the Vertica Python version to 3.13.1 to address CVE-2024-9287. 此版本包含关键安全更新，将 Vertica Python 版本升级到 3.13.1 以解决 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. 修复了加载 JSON 数据时 Vertica 节点崩溃的问题，当某些文件包含 ARRAY 列数据而其他文件不包含时触发。此问题在使用 fjsonparser 的 COPY 操作期间发生。 |
| 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. 修复了 Vertica Management Console 中 License 选项卡显示错误消息和不准确许可证信息的问题。此问题已解决。 |
| 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. 修复了运行 ALTER TABLE 命令时的节点崩溃问题。崩溃由 TieredCatalog 组件中的 VAssert 错误（!inParentCatalog |
| 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. 修复了一个错误：从 Keycloak 用户撤销的角色在用户使用 OAuth 令牌认证后未在 Vertica 中同步撤销。 |