25.1.x Resolved issues¶
25.1.0-9¶
Updated 05/17/2026
| Issue Key | Application Module | Description |
|---|---|---|
| 5332448 | 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. 此前，float 除法计算会生成 INFO 日志记录操作的输入和输出。此输出是多余的，在特定查询中会导致日志文件大小随处理行数线性增长。现在该日志输出已被移除。 |
| 5348438 | 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 的特定组合可能导致内部错误；此问题已解决。 |
| 5382174 | 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（Reflected Cross-Site Scripting XSS 漏洞），影响版本 10.0.1。此前，经过认证的攻击者可利用特定 Web UI 端点中未管理的输入参数注入并执行任意 JavaScript 代码。此更新包含必要的安全增强以缓解该 XSS 漏洞，并确保对用户输入进行适当净化处理。建议用户更新至最新版本以获得安全改进。 |
| 5388716 | Execution Engine | Vertica database nodes and the database itself could experience random crashes during the Mergeout operation, specifically when performing replaydelete for certain tables. A fix has been implemented to ensure the stability and reliability of the Mergeout operation, preventing unexpected database outages. Vertica 数据库节点及数据库本身可能在 Mergeout 操作期间发生随机崩溃，尤其是在对某些表执行 replaydelete 时。已实施修复以确保 Mergeout 操作的稳定性与可靠性，防止意外的数据库宕机。 |
25.1.0-8¶
Updated 04/28/2026
| Issue Key | Application Module | Description |
|---|---|---|
| 5200117 | 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). In order to maintain the sort, we added back the explicit Sort path when we're dealing with a merge join. 24.1 版本新增了一项优化，在兼容的情况下保留哈希/合并右外连接的外表排序。在此工单中，我们发现合并连接中该优化可能导致排序违规（在使用聚合函数时可能产生不一致的结果）。为保持排序，我们在处理合并连接时恢复了显式排序路径。 |
| 5203747 | 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 版本以缓解此问题。 |
| 5203795 | 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 所指定的最长时间。 |
| 5209309 | EON | The server used to determine the transaction log size based off a wrong counter, hence truncating a corrupted transaction file more than necessary. Now, a right counter is used to store the size, hence truncating the last transaction file correctly. 此前服务器基于错误的计数器确定事务日志大小，导致截断了比必要更多的损坏事务文件。现在，使用正确的计数器来存储大小，从而正确截断最后一个事务文件。 |
| 5215119 | 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 读取可靠性。 |
| 5222707 | Optimizer | Internal Optimizer Error (11) with Complex CTE Queries: This release addresses an "Internal Optimizer Error (11)" (specifically isInputTypeCompatibleWithExpected(intype, vartype)) that could occur when executing complex SQL queries involving Common Table Expressions (CTEs) and UNION operations. This issue was observed in Vertica versions v23.4.0-14, v24.4.0-0, and v25.1.0-0. Resolution: The underlying cause of the optimizer error has been identified and resolved, ensuring that such queries now execute as expected without encountering the internal error. Previous Workaround: Previously, users could mitigate this issue by setting the configuration parameter EnableWITHTempRelReuseLimit to '0' or '5'. This workaround is no longer necessary with this fix.复杂 CTE 查询的内部优化器错误（11）：此版本解决了执行涉及公用表表达式（CTE）和 UNION 操作的复杂 SQL 查询时可能出现的「内部优化器错误（11）」。该问题在 Vertica v23.4.0-14、v24.4.0-0 和 v25.1.0-0 中观察到。解决方案：已识别并解决了优化器错误的根本原因，确保此类查询现在可按预期执行而不会遇到内部错误。先前的临时解决方案：用户可以通过将配置参数 EnableWITHTempRelReuseLimit 设置为 0 或 5 来缓解此问题。此修复后不再需要该临时解决方案。 |
| 5225215 | 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 服务器通过其重试机制缓解此类故障。 |
| 5225620 | 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 语句值时的限制一致。 |
| 5228323 | 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 容器镜像的安全性并确保集成和部署的合规性。 |
| 5271173 | Optimizer | In some cases, union sub-queries with coercion could result in type conflicts and an internal error. This issue has been resolved. 在某些情况下，包含类型转换的 union 子查询可能导致类型冲突和内部错误。此问题已解决。 |
| 5297496 | 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 后发现的多个严重和高危安全漏洞。这些修复显著提升了系统的整体安全性。注意：强烈建议用户应用此更新以确保系统免受这些已识别安全风险的影响。 |
| 5335199 | 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() 过程的效率和减少耗时，从而实现更快的系统恢复和改进的整体性能。 |
| 5338237 | 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.1.0-7¶
Updated 03/03/2026
| Issue Key | Application Module | Description |
|---|---|---|
| 4939031 | QA - MC | A fix has been implemented to address an issue where the 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 中正确显示。 |
| 4989562 | 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 |
| 5015455 | 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 不是有效的工具名称。现在，帮助输出已更正为准确显示 Usage: logrotate [options] 以及有效选项列表。 |
| 5079571 | Execution Engine | Replicated tables used to error out when performing cross namespace ILM operations. This issue has been resolved. 复制表在执行跨命名空间 ILM 操作时曾出现错误。此问题已解决。 |
| 5081951 | 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 模式集群之间的基于服务器的复制失败的问题。复制现在可在迁移后的集群和新安装的集群之间正常运行。 |
| 5085486 | Data Networking | A high-severity issue where the Vertica database would hang shortly after upgrading, particularly when MinTLSVersion was set to 3, has been resolved. This fix ensures database stability and prevents SQL queries from becoming stuck on all nodes, restoring normal operation.已解决一个高危问题，即 Vertica 数据库在升级后不久会挂起，特别是在 MinTLSVersion 设置为 3 时。此修复确保数据库稳定性，防止所有节点上的 SQL 查询卡住，恢复正常操作。 |
| 5086372 | Data Networking | TS callback dtor should cleanup without the lock: 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. Now, 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 回调析构函数在锁外执行，从而防止死锁并提高整体系统稳定性。 |
| 5092599 | Backup/DR | Int-String comparison in table expression used to fail VBR and VBR5 restore. This issue has been fixed. 表表达式中的整数字符串比较曾导致 VBR 和 VBR5 恢复失败。此问题已修复。 |
| 5104467 | 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 配置参数，消除了每日的错误消息和误报。 |
| 5107651 | 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 中，重新分片功能在所有扫描中都添加了分段列跟踪，即使不需要时也是如此。修复方案是仅在查询或重新分片场景特别需要时才跟踪分段列。 |
| 5109098 | 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）」的问题。涉及这些复杂视图结构的 UPDATE 查询现在可按预期正常执行。 |
| 5139017 | |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 导致某些查询返回截断的结果——未返回所有预期的行。此功能已被禁用，直至找到根本原因并修复。 |
| 5144016 | UI - Management Console | 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）。 |
| 5181095 | 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 数据和超长字符串，从而恢复数据完整性并消除影响性能的临时解决方案。 |
| 5184562 | Admin Tools | Before this fix, 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 getting the correct and up-to-date catalog information.在此修复之前，AdminTools restart_node 可能选择辅助 UP 节点来运行目录编辑器以获取目录信息。此后，AdminTools restart_node 始终选择主 UP 节点来运行目录编辑器以获取目录信息，确保获取正确且最新的目录信息。 |
| 5202438 | 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] 列。 |
| 5223279 | 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 数据库中创建的远程用户存储位置以进行恢复。 |
25.1.0-6¶
Updated 12/5/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 4562633 | UI - Management Console | DBD upload file permission error: 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 > 新设计 > 手动成功上传查询文件，而不会遇到「权限被拒绝」错误。此修复确保超级用户和所有用户都可以上传文件而无需权限限制。 |
| 4772296 | 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 审计保持一致。 |
| 4854721 | 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 模型成功导入。 |
| 4866839 | Third Party Tools Integration | 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）。 |
| 4876455 | 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 查询不再无限挂起，恢复预期性能。 |
| 4878506 | 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 函数的行为，显著提升了特定场景下的性能。此前，所有输入都被转换为 UTF-16。现在，对于简单区域，STRPOS 使用基于 UTF-8 的比较，避免转换为 UTF-16 并绕过 ICU 库，实现更快的执行。 |
| 4893665 | 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 列）的问题。模型现在能使用预期的输入特征数量进行正确预测。 |
| 4902083 | Hadoop, ResourceManager | Resolved an issue where Vertica clusters would experience a timeout and core dump during startup after an upgrade from version 12.0.4 to 25.1. This problem specifically occurred during disk space information refresh and storage location creation, impacting environments with replicated S3 buckets and HDFS storage. The fix ensures successful database initialization and proper handling of storage locations in Vertica Analytic Database v25.1.0-6. 解决了从 12.0.4 升级到 25.1 后 Vertica 集群在启动期间超时并核心转储的问题。此问题在磁盘空间信息刷新和存储位置创建期间发生，影响具有复制 S3 存储桶和 HDFS 存储的环境。修复确保在 Vertica v25.1.0-6 中成功进行数据库初始化并正确处理存储位置。 |
| 4904536 | Catalog Engine | Certain complex queries using internal temp relations in their plans could either error or output duplicate rows. This issue has been resolved. 某些在计划中使用内部临时关系的复杂查询可能出现错误或输出重复行。此问题已解决。 |
| 4950425 | 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 conversions. Specifically, the node would crash during COPY operations when using TO_CHAR with formats like 'YYYYMMDD', 'FMDay, FMDD HH12:MI:SS', etc. This fix ensures stability when using fault-tolerant expressions with FILLER and TO_CHAR functions. 修复了启用 CopyFaultTolerantExpressions 参数且 FILLER 与特定 TO_CHAR 转换一起使用时节点宕机的问题。此修复确保在使用容错表达式与 FILLER 和 TO_CHAR 函数时的稳定性。 |
| 4970329 | Security | Fixed an issue where creating access policies added extra parentheses, causing COPY_TABLE to fail with an access policy mismatch error. 修复了创建访问策略时添加了额外括号，导致 COPY_TABLE 因访问策略不匹配错误而失败的问题。 |
| 4980425 | 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 正确处理令牌过期和重试，防止错误和目录同步问题。 |
| 5006749 | 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 内存使用持续增长。此修复解决了影响所有主机的内存泄漏问题。 |
| 5008271 | Optimizer | Previously when comparing string literals cast to array with LIKE ANY/ALL (i.e. select 'foo' like any ('bar'::Array[varchar]);) Vertica would improperly locate string array data in memory and cause a fatal crash. This no longer happens. 此前，当使用 LIKE ANY/ALL 比较强制转换为数组的字符串字面量时，Vertica 会在内存中错误定位字符串数组数据并导致致命崩溃。此问题已不再发生。 |
| 5012269 | 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 客户端认证才能登录。 |
| 5047814 | 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 二进制文件中发现了关键安全漏洞并已修复。 |
| 5048882 | Admin Tools | This fix ensures the upgrade process is successful and correctly handles the FlexTableLib library, resolving the fjsonparser incompatibility issue. 此修复确保升级过程成功并正确处理 FlexTableLib 库，解决了 fjsonparser 不兼容的问题。 |
25.1.0-5¶
Updated 07/02/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 4636969 | Optimizer | Historically, the statistics histogram would be invalidated if the row count was updated without fully reanalyzing the columns; this invalidation no longer happens. 历史上，如果行计数更新而未完全重新分析列，统计信息直方图将失效。此失效情况已不再发生。 |
25.1.0-4¶
Updated 06/24/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 4634966 | Kafka Integration | The Kafka scheduler was failing to create on both FIPS and non-FIPS systems after upgrading to Vertica 25.1 This issue has been resolved. 升级到 Vertica 25.1 后，Kafka 调度程序在 FIPS 和非 FIPS 系统上均创建失败。此问题已解决。 |
| 4730767 | 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。 |
| 4777392 | Data Collector | Fixed an issue where comments added to table columns were not being reflected in the remarks column of the jdbc_columns table. This update ensures that column comments are properly synchronized. 修复了添加到表列的注释未在 jdbc_columns 表的 remarks 列中反映的问题。此更新确保列注释正确同步。 |
| 4805905 | Control Networking | The Vertica upgrade process has been enhanced to allow for co-existence of different Vertica versions within the same cluster during rolling upgrades. This is achieved through an override mechanism that specifies compatible build hashes, enabling administrators to perform manual online upgrades with less disruption. Vertica 升级过程已增强，允许在滚动升级期间同一集群中不同 Vertica 版本共存。这是通过指定兼容构建哈希的覆盖机制实现的，使管理员能够以较少中断执行手动在线升级。 |
| 4810716 | Linux, PCx86 | 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 文件且字符串字段中包含转义字符的特定场景中，解析后的字符串值可能缺少几个字符。此问题已解决。 |
| 4832011 | Data load / COPY | A fix has been implemented to address an issue where a Vertica node would crash when loading JSON data containing inconsistent ARRAY column values (some files with data, others without). The crash occurred specifically when loading a mix of JSON files where some contained data for the ARRAY column and others did not. This issue has been resolved. 已实施修复以解决加载包含不一致 ARRAY 列值的 JSON 数据时 Vertica 节点崩溃的问题。此问题已解决。 |
| 4837349 | Execution Engine | Certain complex queries using internal temp relations in their plans could either error or output duplicate rows. This issue has been fixed. 某些在计划中使用内部临时关系的复杂查询可能出现错误或输出重复行。此问题已修复。 |
25.1.0-3¶
Updated 04/01/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 4522089 | Third Party Tools Integration | We have upgraded the rsync connection for Linux file systems 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。 |
| 4523911 | EON | The UsePeerToPeerDataTransfer knob can now be enforced at the node level. UsePeerToPeerDataTransfer 参数现在可以在节点级别强制执行。 |
| 4535433 | 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」的警告消息条目。此消息并不表示真正的问题，因此已被移除。 |
| 4536639 | Database Designer Core, Refresh | An issue that was blocking the ability to run historical queries at epochs prior to the Ancient History Mark, while running the Refresh command, has been resolved. 解决了在运行 Refresh 命令时，无法在 Ancient History Mark 之前的 epoch 运行历史查询的问题。 |
25.1.0-2¶
Updated 03/24/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 4404831 | Backup/DR | An issue occurred where if a Vertica node was down, vbr would fail. This issue has been resolved. Now, the backup location points to the same host as the Vertica node. 修复了如果 Vertica 节点宕机，vbr 会失败的问题。现在，备份位置指向与 Vertica 节点相同的主机。 |
| 4444326 | License | Depending on the number of nodes in the cluster, a license expiration NOTICE message was appearing repeatedly. Now, the server reports this NOTICE message a limited number of times. 根据集群中节点的数量，许可证过期 NOTICE 消息会重复出现。现在，服务器报告此 NOTICE 消息的次数有限。 |
| 4449031 | Admin Tools, Backup/DR | Added IMDSv2 support for config setup at db start. 在数据库启动时添加了对 IMDSv2 配置设置的支持。 |
| 4491417 | Kafka Integration | An issue that was causing nodes to crash after upgrade in librdkafka has been resolved. 解决了升级后 librdkafka 导致节点崩溃的问题。 |
25.1.0-1¶
Updated 03/14/2025
| Issue Key | Application Module | Description |
|---|---|---|
| 4350656 | Installation Program | Installing Vertica on Amazon 2023 Linux fails and an error message is displayed. 在 Amazon 2023 Linux 上安装 Vertica 失败并显示错误消息。 |
| 4392278 | 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。 |
| 4393188 | Directed Query | Directed query search could fail to match in cases where the predicate included {{CONST op CONST.. This issue has been resolved. 在谓词包含 {{CONST op CONST}} 的情况下，定向查询搜索可能无法匹配查询。此问题已解决。 |
| 4403815 | Scrutinize, Vcluster | System table data from vcluster scrutinize now has column headers in the retrieved files. 来自 vcluster scrutinize 的系统表数据现在在检索到的文件中包含列标题。 |
25.1.0-0¶
Updated 01/16/2025
| Issue Key | Component | Description |
|---|---|---|
| VER-87686 | Client Drivers - JDBC | executeLargeUpdate returns an incorrect row count. This is caused by a bug in Simba SDK. Upgrade to the latest upgrade of Simba SDK to resolve this issue. executeLargeUpdate 返回不正确的行计数。这是由 Simba SDK 中的错误引起的。已升级到最新的 Simba SDK 以解决此问题。 |
| VER-90265 | Kafka Integration | Running the vkconfig shutdown command with the "-conf" option would sometimes erroneously shutdown all running vkconfig instances and not just the ones started with the specified configuration. This issue is now fixed. 使用 -conf 选项运行 vkconfig shutdown 命令有时会错误地关闭所有正在运行的 vkconfig 实例，而不仅仅是使用指定配置启动的实例。此问题现已修复。 |
| VER-93594 | Optimizer | An issue occurred, where a join spill was happening when processing the optimized delete part of the plan, which disallows Filter/Filter join distribution. Since the join inner was too large to fit in memory, an error was returned with a hint to retry with Filter/Filter enabled, even though it was already enabled in the session. This issue has been resolved; to address this, when the EnableFilterFilter hint is encountered when it's already enabled, we check if it's an optimized delete plan and in that case retry with optimized delete disabled, allowing the optimizer to choose a Filter/Filter join distribution. 修复了处理计划中优化删除部分时发生的连接溢出问题，该问题禁止 Filter/Filter 连接分布。由于连接内部数据过大无法放入内存，返回了带提示的错误。此问题已解决。 |
| VER-93700 | DDL | An issue occurred where the CREATE TABLE syntax using INCLUDING PROJECTIONS creates new pin policies. The CREATE TABLE syntax has been changed to allow user excludes storage policies when running CREATE TABLE... LIKE to copy the table structure from existing table. 修复了使用 INCLUDING PROJECTIONS 的 CREATE TABLE 语法创建新的固定策略的问题。CREATE TABLE 语法已更改，允许用户在运行 CREATE TABLE...LIKE 从现有表复制表结构时排除存储策略。 |
| VER-93842 | Logging | Old trace profile (.prof) files were not deleted filling up the disk space. A new functionality was added to the do_logrotate() meta function and LogRotateTask Timer serivce that deletes an existing profile if it is older than the max_age (7 days by default). 旧的跟踪配置文件（.prof）文件未被删除，导致磁盘空间被填满。已向 do_logrotate() 元函数和 LogRotateTask Timer 服务添加新功能，删除超过 max_age（默认为 7 天）的现有配置文件。 |
| VER-94182 | UI - Management Console | Security Enhancement: Both /opt/vconsole/temp and /opt/vconsole/tempkc directories created by MC have had their permissions change to 750 (drwxr-x---). 安全增强：MC 创建的 /opt/vconsole/temp 和 /opt/vconsole/tempkc 目录的权限已更改为 750（drwxr-x---）。 |
| VER-94621 | UI - Management Console | In MC v11.0, the Query Profile page was working without any issues. MC v12.0 was localized and all labels were translated. However, the Query Profile page was not localized by oversight. This issue has been resolved. 在 MC v11.0 中，Query Profile 页面正常工作。MC v12.0 已本地化并翻译了所有标签，但 Query Profile 页面被疏忽未翻译。此问题已解决。 |
| VER-95684 | Kafka Integration, UDX | In earlier releases, providing a value for the "enable_chunker" parameter had a negative impact on system performance. This issue is now resolved. The "enable_chunker" parameter is set to "True" resulting in improved system performance. 在早期版本中，提供 enable_chunker 参数值对系统性能有负面影响。此问题现已解决。enable_chunker 参数设置为 True，从而提高了系统性能。 |
| VER-95698 | Data load / COPY | Fixed a bug that may cause errors when loading more than 8k files at once using EXECUTE DATA LOADER. 修复了使用 EXECUTE DATA LOADER 一次加载超过 8k 文件时可能导致错误的 bug。 |
| VER-95699 | Data load / COPY | Performance improvement: Loading a small amount of files using EXECUTE DATA LOADER WITH FILES when the folder contains a large amount of files should be much faster now, especially when the source location is an object store. 性能改进：当文件夹中包含大量文件时，使用 EXECUTE DATA LOADER WITH FILES 加载少量文件应该更快，特别是当源位置是对象存储时。 |
| VER-95880 | EON | To avoid potential FNF or leaked files, an issue was fixed by scanning all storages in the snapshot to restore/replicate, and removing the storages from tombstone and the reaper queue, while keeping others untouched in tombstone/reaper queue. 为避免潜在的 FNF 或文件泄漏，通过扫描快照中的所有存储以进行恢复/复制，并从墓碑和 reaper 队列中移除存储，同时保持其他存储不变，修复了此问题。 |
| VER-95925 | Data load / COPY | Previously, when querying certain ORC/Parquet files in a certain way, a hang would occur. This issue has been resolved. 此前，以特定方式查询某些 ORC/Parquet 文件时会发生挂起。此问题已解决。 |
| VER-96299 | Optimizer | Between v12 and v24, a previous bug fix made it so that null rows passed hash SIP filters. This led to a performance drop on queries that relied on SIPS to filter out nulls early. This has been resolved; now, SIP filters remove null rows again. 在 v12 和 v24 之间，先前的 bug 修复使空行通过了哈希 SIP 过滤器。这导致依赖 SIPS 早期过滤空值的查询性能下降。此问题已解决；SIP 过滤器现在再次移除空行。 |
| VER-96309 | Data load / COPY | Previously, expanding wild cards as part of COPY command failed on systems with certain versions of GLIBC. This issue has now been fixed. 此前，在具有某些版本 GLIBC 的系统上，作为 COPY 命令一部分的通配符扩展失败。此问题现已修复。 |
| VER-96377 | Admin Tools, Installation Program, Installation: Server RPM/Deb | urllib3 version is now upgraded from 1.26.18 to 1.26.19 urllib3 版本已从 1.26.18 升级到 1.26.19。 |
| VER-96445 | Security | Clients not sending packets during initialization of TLS connections will no longer cause CPU usage to spike. 在 TLS 连接初始化期间不发送数据包的客户端将不再导致 CPU 使用率飙升。 |
| VER-96459 | Backup/DR | If we point the --communal-storage-location at the root of a bucket, and without a trailing slash, the show-restore-points does not automatically add the trailing slash when handling the path. We fixed this issue by canonicalize the path when we get it from the show-restore-points command. 如果将 --communal-storage-location 指向存储桶根目录且不带尾部斜杠，show-restore-points 在处理路径时不会自动添加尾部斜杠。我们通过在从 show-restore-points 命令获取路径时规范化路径来修复此问题。 |
| VER-96609 | Execution Engine | In some cases, FCSVParser used to core dump when loading multiple files with glob patterns. The issue was resolved. 在某些情况下，FCSVParser 在使用 glob 模式加载多个文件时曾发生核心转储。此问题已解决。 |
| VER-96728 | Installation Program | nofile check does not work when installing Vertica on Ubuntu 18.04. This essue has been fixed. We are setting the nofile value via python module resource if the value is less than the recommended value. 在 Ubuntu 18.04 上安装 Vertica 时，nofile 检查不起作用。此问题已修复。如果 nofile 值小于推荐值，我们通过 Python 模块 resource 设置 nofile 值。 |
| VER-97123 | Optimizer | The view referenced in the UPDATE's target list had its subquery pruned during query rewrite, which misaligned a predicate reference to it and caused it to return a null value. This issue has been resolved; now, subquery targets are not pruned from the top-level UPDATE query's target list, instead only pruning FROM subqueries. UPDATE 目标列表中引用的视图在查询重写期间其子查询被修剪，导致对它的谓词引用不对齐并返回空值。此问题已解决。 |
| VER-97203 | HTTP | HSTS header was missing from the HTTPS Server. After the fix, Vertica Embedded HTTPS service enforces HSTS header. HTTPS 服务器缺少 HSTS 标头。修复后，Vertica 嵌入式 HTTPS 服务强制执行 HSTS 标头。 |
| VER-97299 | Client Drivers - VSQL | There was an issue that was preventing disabling or enabling of subcluster interior load balancing from taking effect immediately because an internal cache was not being cleared. Using ALTER DATABASE to set the EnableInteriorLoadBalancing parameter would have no impact on the result of the DESCRIBE_LOAD_BALANCE_DECISION function, which in turn would not change load balancing behavior of clients. This problem has been resolved. 存在一个问题：由于内部缓存未清除，子集群内部负载均衡的禁用或启用无法立即生效。此问题已解决。 |
| VER-97476 | Procedural Languages | On Eon mode as of 24.3, stored procedures triggered by the scheduler could not see the current subscriptions, leading to failures for certain procedures. This has been resolved; now, scheduled stored procedures can see the subscriptions. 在 24.3 版本的 Eon 模式下，由调度程序触发的存储过程无法看到当前订阅，导致某些过程失败。此问题已解决；现在，定时存储过程可以查看订阅。 |
| VER-97680 | Execution Engine | Previously, the priority field was not persisting in the catalog. When the database was restarted, the default value of 0 would be applied to every rule. Now, the priority field is accounted for and persists. 此前，priority 字段未在目录中持久化。当数据库重启时，默认值 0 会应用于每个规则。现在，priority 字段已被考虑并持久化。 |
| VER-97700 | License | In some cases, automated database size audits used to run at a different time of the day from the one specified by GET_AUDIT_TIME. The issue has been resolved. 在某些情况下，自动数据库大小审计的运行时间与 GET_AUDIT_TIME 指定的时间不同。此问题已解决。 |
| VER-97819 | DDL | The knobs for Health Watchdog were not available. The knobs added for the watchdog metrics are now guided and documented. Health Watchdog 的参数之前不可用。现已添加 watchdog 指标的参数并进行文档说明。 |
| VER-98563 | 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 fixed. 在多查询层级使用 WITH 语句且每层具有不同目标列表的查询有时会返回错误。此问题已修复。 |