26.1.x Resolved issues

26.1.0-6

Updated 6/8/2026

Issue Key	Application Module	Description
5347051	UI - Management Console	On AArch64 systems (e.g., RHEL8 aarch64), the Vertica Management Console RPM bundled an OpenJDK distribution compiled for an incorrect architecture. This prevented the Vertica Management Console from starting, and no mconsole.log file was generated. This issue is now resolved. 在 AArch64 系统（如 RHEL8 aarch64）上，Vertica Management Console RPM 捆绑了针对错误架构编译的 OpenJDK 发行版。这导致 Vertica Management Console 无法启动，且不会生成 mconsole.log 文件。此问题现已解决。
5384511	Execution Engine	Fixed an issue with reused Common Table Expressions (CTEs) when they are referenced in multiple distinct aggregate clauses. Previously, the way we handled pruning in these cases could lead to inconsistent results; now, we prune the CTE at the top level to ensure the entire query has the correct column references. 修复了重用公共表表达式（CTE）在多个不同聚合子句中引用时的问题。此前，这些情况下的裁剪处理方式可能导致结果不一致；现在我们在顶层裁剪 CTE，确保整个查询具有正确的列引用。
5388143	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. 此更新修复了 Vertica 数据库服务器使用的 gRPC 依赖中发现的关键安全漏洞 CVE-2026-33186。
5389094	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. 此更新修复了关键安全漏洞 CVE-2025-12453（反射型跨站脚本攻击 XSS），该漏洞影响 Vertica 10.0.1 版本。此前，认证攻击者可利用某些 Web UI 端点的未管理输入参数注入并执行任意 JavaScript 代码。此更新包含必要的安全增强，以缓解已识别的 XSS 漏洞，并确保对用户输入进行适当的净化和中性化处理，防止恶意脚本执行。
5418946	Security	This update addresses multiple high-severity CVEs identified in various third-party components bundled with Vertica. 此更新修复了 Vertica 捆绑的多个第三方组件中发现的多个高危 CVE。
5453399	Execution Engine	Queries employing the LISTAGG aggregate function with the WITHIN GROUP clause were experiencing high network data transfer and prolonged execution times due to excessive buffer allocation. This was leading to severe performance degradation for the affected query and other concurrent database operations, potentially causing database instability or halts. This update provides significant improvements to both memory and time performance by fixing the buffer allocation. 使用 LISTAGG 聚合函数配合 WITHIN GROUP 子句的查询因缓冲区过度分配而出现高网络数据传输和长时间执行的问题。这导致受影响的查询及其他并发数据库操作性能严重下降，可能造成数据库不稳定或宕机。此更新通过修复缓冲区分配，显著改善了内存和时间性能。

26.1.0-5

Updated 4/29/2026

Issue Key	Application Module	Description
5333348	Backup/DR	Improved Snapshot Loading Performance: This fix includes an optimization to the load_snapshot() process, specifically addressing inefficiencies within restoreScanObjects(). Previously, redundant CRC checks for existing storage bundles and repeated storage location validations could significantly prolong snapshot loading times, sometimes up to 4 hours on certain nodes. With this update, these checks have been streamlined, leading to a notable reduction in the time required to load snapshots, particularly in scenarios involving replicated or restored data with common storage containers. 快照加载性能优化：此修复优化了 load_snapshot() 过程，特别解决了 restoreScanObjects() 中的效率问题。此前，对现有存储 bundle 的冗余 CRC 检查以及重复的存储位置验证会显著延长快照加载时间，在某些节点上有时长达 4 小时。此更新简化了这些检查，显著减少了加载快照所需的时间，特别是在涉及复制或恢复数据且具有公共存储容器的场景中。
5330806	Client Drivers - ODBC, Client Drivers - VSQL	Vertica 26.x Client Driver Connectivity with SSL-Enabled Servers: This release includes a fix for a critical issue affecting Vertica 26.1.0-3 client drivers (ODBC and vsql). Previously, these drivers failed to establish connections when the Vertica server had SSL enabled, leading to application crashes or silent exits. This resolution ensures stable and secure connectivity for Vertica 26.x clients operating in SSL-configured environments. Vertica 26.x 客户端驱动与启用 SSL 的服务器的连接：此版本修复了影响 Vertica 26.1.0-3 客户端驱动（ODBC 和 vsql）的关键问题。此前，当 Vertica 服务器启用 SSL 时，这些驱动无法建立连接，导致应用程序崩溃或静默退出。此修复确保了 Vertica 26.x 客户端在 SSL 配置环境中的稳定安全连接。
5333789	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 错误。

26.1.0-4

Updated 4/07/2026

Issue Key	Application Module	Description
5299503	Admin Tools	This update addresses critical and high-severity security vulnerabilities (Defect ID: 5299503) that were identified following an upgrade to version 23.4.0-23. This fix resolves various CVEs, including CVE-2025-68121 (Critical) and multiple high-severity CVEs, significantly improving the security of the system. 此更新修复了升级到 23.4.0-23 后发现的严重和高危安全漏洞（缺陷 ID：5299503）。此修复解决了多个 CVE，包括 CVE-2025-68121（严重）和多个高危 CVE，显著提升了系统安全性。
5301663	EON	A new internal knob called RemoveBadRestorePointsOnStartup is added to allow progress of startup in the presence of bad restore points if enabled. 新增一个名为 RemoveBadRestorePointsOnStartup 的内部开关，启用后允许在存在损坏恢复点时继续启动进程。

26.1.0-3

Updated 3/24/2026

Issue Key	Application Module	Description
5181232	DDL - Table	Previously, a scheduled stored procedure would execute with a different default value for standardConformingStrings. This would produce differing results than a stored procedure executing using the CALL functionality if the stored procedure query contained usage of backslash impacted by the setting of standardConformingStrings. Now it is aligned with the same default value as user sessions. 此前，定时执行的存储过程会使用不同的 standardConformingStrings 默认值，导致与使用 CALL 功能执行的存储过程产生不同结果（如果存储过程查询包含受 standardConformingStrings 设置影响的反斜杠用法）。现在已与用户会话的默认值保持一致。
5196644	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 版本新增了一项优化，在兼容的情况下保留哈希/合并右外连接的外表排序。在此工单中，我们发现合并连接中该优化可能导致排序违规（在本例中会在使用聚合函数时产生不一致的结果）。为保持排序，我们在处理合并连接时恢复了显式排序路径。
5249096	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 在处理投影时可能遇到内部类型不匹配，导致优化器断言失败。此问题已解决。
5271172	Optimizer	In some cases, union sub-queries with coercion could result in type conflicts and an internal error. This issue has been resolved. 在某些情况下，包含类型转换的 union 子查询可能导致类型冲突和内部错误。此问题已解决。
5286466	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 issue has been resolved. 对包含用户自定义函数的复杂/嵌套复杂类型添加了过于严格错误处理。这导致一些有效的 SQL 错误地报告「不支持」错误。此问题已解决。

26.1.0-2

Updated 3/12/2026

Issue Key	Application Module	Description
5203793	Catalog Engine	Concurrent sequence generation in OCC lock mode can now tolerate LockTimeout setting to zero. Instead of immediately failing, they now wait for the maximum amount of time given by LockTimeout and a new knob called MinOCCLockTimeout. OCC 锁定模式下的并发序列生成现在可以容忍 LockTimeout 设置为零。它们不再立即失败，而是等待 LockTimeout 和新参数 MinOCCLockTimeout 所指定的最长时间。
5206312	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 版本以缓解此问题。
5215117	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 读取可靠性。
5222639	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 语句值时的限制一致。
5224246	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 older version enterprise database for reviving. 修复前，Kubernetes operator 在恢复从 10.x Enterprise 数据库迁移的 Eon 数据库时，遇到远程用户存储位置可能会报错。修复后，Kubernetes operator 能正确处理旧版本 Enterprise 数据库中创建的远程用户存储位置以进行恢复。
5225170	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 服务器通过其重试机制缓解此类故障。

26.1.0-1

Updated 2/26/2026

Issue Key	Application Module	Description
5181096	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 数据和超长字符串，从而恢复数据完整性并消除影响性能的临时解决方案。
5196883	Installation Program	Previously, the install_vertica and update_vertica scripts would fail to correctly apply the --ssh-password option, leading to unresponsiveness or hanging during installations and upgrades when passwordless SSH was not configured. This fix ensures that the --ssh-password option is now properly recognized and utilized, allowing for successful script execution without requiring temporary passwordless SSH. 此前，install_vertica 和 update_vertica 脚本无法正确应用 --ssh-password 选项，在未配置免密 SSH 时导致安装和升级过程中无响应或挂起。此修复确保 --ssh-password 选项被正确识别和使用，允许在无需临时配置免密 SSH 的情况下成功执行脚本。
5215373	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 容器镜像的安全性并确保集成和部署的合规性。

26.1.0-0

Updated 1/30/2026

Issue Key	Application Module	Description
4341124	Catalog Engine	An issue was discovered with Vertica clusters, where a node attempting to join would fail with an 'Invalid buffer enlargement request size' error during the cluster invitation process, specifically during catalog serialization. This issue has been resolved, and the fix ensures successful node integration and cluster stability. 修复了 Vertica 集群中的一个问题：在集群邀请过程中，尝试加入的节点会在目录序列化时失败，报错「无效的缓冲区扩容请求大小」。此修复确保节点成功集成和集群稳定性。
4348762	UI - Management Console	This fix addressed an issue where Management Console (MC) was sending spurious 'Failed Query Number' email alerts and failing to provide rejection details for certain queries, such as EXPORT TO VERTICA statements, leading to false positives and unnecessary email notifications. This issue has been resolved. 此修复解决了 Management Console（MC）发送虚假的「失败查询数量」邮件警报，且未能为某些查询（如 EXPORT TO VERTICA 语句）提供拒绝详情的问题，导致误报和不必要的电子邮件通知。此问题已解决。
4404849	Client Drivers - Python	Fixed an issue that occurred when users attempted to import the stumpy Python library within User Transform Functions (UTDFs). With this fix, users can now successfully import and utilize the stumpy library and its dependencies within their Python UTDFs. 修复了用户在用户转换函数（UTDF）中尝试导入 stumpy Python 库时出现的问题。此修复后，用户可以在 Python UTDF 中成功导入和使用 stumpy 库及其依赖项。
4524035	System: Performance	Query Performance Improvement for RLE-Encoded Data: Addresses a performance degradation issue that was observed, specifically for queries involving tables with RLE and non-RLE segmented columns. This fix optimizes the query planner's handling of data subdivisions, resulting in improved execution times for affected queries. RLE 编码数据的查询性能改进：解决了观察到的性能下降问题，特别是涉及同时包含 RLE 和非 RLE 分段列的表的查询。此修复优化了查询计划器对数据细分的处理，从而缩短了受影响查询的执行时间。
4536627	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 内存使用持续增长，即使空闲的从子集群也是如此。此修复解决了影响所有主机的内存泄漏问题，无论硬件规格或操作系统如何。
4812173	Security	Addressed a security vulnerability (ID: 4812173) related to an outdated WSGIServer component (version 0.5) identified during security scans on AIOps servers, specifically impacting Vertica. This update enhances the system's security posture. 修复了在 AIOps 服务器的安全扫描中发现的与旧版 WSGIServer 组件（版本 0.5）相关的安全漏洞（ID：4812173），该漏洞特别影响 Vertica。此更新增强了系统的安全性。
4830176	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 比较强制转换为数组的字符串字面量时（例如 select 'foo' like any ('bar'::Array[varchar])），Vertica 会在内存中错误定位字符串数组数据并导致致命崩溃。此问题已不再发生。
4847984	System: Performance	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 函数的行为，显著提升了特定场景下的性能。变更内容：此前，所有 STRPOS 的输入都被转换为 UTF-16 以利用 ICU（Unicode 国际组件）库进行字符串比较。虽然 ICU 为复杂的区域感知比较提供了 robust 支持，但这种转换引入了开销，特别是对于简单用例。现在，对于具有 1 对 1 字符映射的简单区域（如 en_US、de_D 等每个字符在 UTF-8 和 UTF-16 之间直接映射而无需规范化或多码点处理的区域），STRPOS 使用基于 UTF-8 的比较，避免了转换为 UTF-16 并完全绕过了 ICU 库，从而实现更快的执行速度。
4862319	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）」的问题。涉及这些复杂视图结构的更新查询现在可按预期正常执行。
4864875	Optimizer	Database Stability Improvement for LIKE ANY Queries: A critical issue that could cause Vertica databases to crash when executing queries containing the pattern LIKE ANY ('%string%'::ARRAY[Varchar]) has been resolved. This fix enhances database stability and prevents unexpected outages, particularly for complex queries involving explicit array casting with LIKE ANY. LIKE ANY 查询的数据库稳定性改进：已解决一个关键问题，即执行包含 LIKE ANY ('%string%'::ARRAY[Varchar]) 模式的查询时可能导致 Vertica 数据库崩溃。此修复增强了数据库稳定性，防止意外宕机，特别是对于涉及显式数组强制转换的 LIKE ANY 复杂查询。
4880668	DDL - Table	Fixed an issue where functions, such as regexp_substr, used within stored procedures would incorrectly return NULL when the stored procedure was executed via a schedule. This behavior was observed despite the functions working as expected when the stored procedure was called directly or through EXECUTE_TRIGGER. 修复了存储过程中使用的函数（如 regexp_substr）在通过计划任务执行时错误返回 NULL 的问题。此问题在直接调用存储过程或通过 EXECUTE_TRIGGER 执行时并未出现。
4917190	Optimizer	An issue with performance degradation was observed in queries utilizing WITH clauses when migrating from Vertica 10.x to newer versions (24.x and 25.x) in an EON mode database environment. This issue has been resolved. 解决了在 EON 模式数据库环境中从 Vertica 10.x 迁移到新版本（24.x 和 25.x）时，使用 WITH 子句的查询出现性能下降的问题。此问题已解决。
4990806	Admin Tools	Fixed an issue where the fjsonparser() function in FlexTableLib became incompatible (SDK version mismatch) after upgrading to Vertica 25.3. 修复了升级到 Vertica 25.3 后，FlexTableLib 中的 fjsonparser() 函数出现 SDK 版本不匹配的问题。
4990862	Vcluster	Vcluster CLI now supports kill_host and kill_node commands, enabling users to terminate database processes on specified hosts directly from the command line. This enhancement is part of the ongoing effort to transition Vcluster into a comprehensive replacement for AdminTools. Vcluster CLI 现在支持 kill_host 和 kill_node 命令，用户可以直接从命令行终止指定主机上的数据库进程。此增强是 Vcluster 逐步成为 AdminTools 全面替代方案的一部分。
5001398	Client Drivers - JDBC	The Vertica JDBC driver has been updated to enable full support for TLS 1.3, ensuring compliance with security requirements. Vertica JDBC 驱动已更新，完全支持 TLS 1.3，确保符合安全要求。
5008290	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 处理，即他们只能使用已显式授予的认证方法。
5022179	Backup/DR	Previously, customers attempting to replicate data from Azure-based Vertica clusters to on-premise environments experienced failures with an "Error deserializing objects" (Code: 3196) during the REPLICATE command. This fix resolves the underlying deserialization problem, ensuring successful and reliable data synchronization between Vertica clusters. 此前，尝试将基于 Azure 的 Vertica 集群中的数据复制到本地环境时，在 REPLICATE 命令期间出现「反序列化对象错误」（代码：3196）而失败。此修复解决了底层的反序列化问题，确保 Vertica 集群之间成功可靠的数据同步。
5028767	UI - Management Console	Addressed an issue where Vertica agents failed to start, leading to Management Console dashboards not loading and 'Error occurred while getting database thresholds null'.The fix ensures agents start successfully, restoring full Management Console functionality. 解决了 Vertica 代理无法启动的问题，导致 Management Console 仪表板无法加载并出现「获取数据库阈值时出错 null」。修复确保代理成功启动，恢复完整的 Management Console 功能。
5040970	License	Resolved an issue where the audit system inaccurately reported data utilization, leading to inflated license usage figures. The audit now correctly reflects actual data size. 解决了审计系统不准确地报告数据使用量导致许可证用量虚高的问题。审计现在正确反映实际数据大小。
5046044	Data Networking	Resolved an issue where Vertica databases, after upgrading to version 25.3.0-2, would experience hangs, causing all SQL queries on nodes to become stuck. This instability was particularly observed when TLS 1.3 was configured (ALTER DATABASE DEFAULT SET MinTLSVersion = 3;). This fix addresses the database hanging behavior, improving overall system stability post-upgrade. 解决了 Vertica 数据库升级到 25.3.0-2 后出现挂起，导致节点上所有 SQL 查询卡住的问题。在配置了 TLS 1.3（ALTER DATABASE DEFAULT SET MinTLSVersion = 3;）时尤其容易发生此不稳定现象。此修复解决了数据库挂起行为，提升了升级后的整体系统稳定性。
5051561	UI - Management Console	Resolved an issue where the "Upload From File" caption would disappear, appearing as a blank blue area, after uploading a query file in the Database Designer (DBD). This display anomaly was particularly observed following an upgrade to MC version 25.2.0-3, and no longer occurs. 解决了在 Database Designer（DBD）中上传查询文件后，「Upload From File」标题消失、显示为空白蓝色区域的问题。此显示异常在升级到 MC 25.2.0-3 后尤为明显，现已不再发生。
5051975	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 配置参数，消除了每日的错误消息和误报。
5062092	Backup/DR	Int-String comparison in table expression used to fail VBR and VBR5 restore. This issue has been fixed. 表表达式中的整数字符串比较曾导致 VBR 和 VBR5 恢复失败。此问题已修复。
5079472	UI - Management Console	Resolved an issue that prevented successful provisioning of Vertica nodes from the Management Console portal in Google Cloud Platform (GCP). Users encountered errors such as 'No inventory was parsed' or 'provided hosts list is empty' during cluster creation, even for single nodes. This fix ensures reliable node provisioning in affected GCP regions. 解决了在 Google Cloud Platform（GCP）中无法从 Management Console 门户成功配置 Vertica 节点的问题。用户在创建集群时遇到「未解析到清单」或「提供的主机列表为空」等错误，即使对于单节点也是如此。此修复确保在受影响的 GCP 区域中实现可靠的节点配置。
5079567	Catalog Engine	Replicated tables used to error out when performing cross namespace ILM operations. This issue has been fixed. 复制表在执行跨命名空间 ILM 操作时曾出现错误。此问题已修复。
5080026	Security, Third Party Tools Integration	Addressed multiple critical and high-severity vulnerabilities (CVEs) identified by image security scanners in Vertica server v25.3.0-2 and Vertica Operator v25.3.0-0, enhancing the overall security posture of the system. 解决了 Vertica 服务器 v25.3.0-2 和 Vertica Operator v25.3.0-0 的镜像安全扫描器发现的多个严重和高危漏洞（CVE），增强了系统的整体安全性。
5080185	Execution Engine	Fixed an issue where a database node could crash unexpectedly when importing a malformed directed query file using the IMPORT_DIRECTED_QUERIES function. Previously, truncated files or those missing critical delimiters (like a semicolon) could lead to a node crash. This fix enhances the robustness of the IMPORT_DIRECTED_QUERIES function, improving system stability when handling improperly formatted input files. 修复了使用 IMPORT_DIRECTED_QUERIES 函数导入格式错误的定向查询文件时数据库节点可能意外崩溃的问题。此前，截断的文件或缺少关键分隔符（如分号）的文件可能导致节点崩溃。此修复增强了 IMPORT_DIRECTED_QUERIES 函数的健壮性，提高了处理格式不当输入文件时的系统稳定性。
5080219	Vcluster	Resolved an issue where the vcluster stop_db command would get stuck in a verification loop, leading to timeouts and an incomplete database shutdown. The command now correctly processes node status during the shutdown sequence. 解决了 vcluster stop_db 命令陷入验证循环导致超时和数据库无法完全关闭的问题。该命令现在能在关闭序列中正确处理节点状态。
5080801	Data Networking	Resolved a potential deadlock scenario where TS callback destructors (dtors) were executing while holding a lock. This fix ensures that callback dtors now run outside the lock, preventing deadlocks that could occur, for example, with async Messenger notifiers 解决了 TS 回调析构函数在持有锁时执行可能导致死锁的问题。此修复确保回调析构函数在锁外运行，防止可能发生的死锁（例如异步 Messenger 通知器场景）。
5082078	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 时光标恢复正常，防止终端显示问题。
5088984	UI - Management Console	Previously, the 'Upgrade MC' option within the management console did not display versions 25.2 and later as available for upgrade. This issue has been resolved, and users can now access the latest versions for upgrading their management console. 此前，Management Console 中的「Upgrade MC」选项未显示 25.2 及更高版本可供升级。此问题已解决，用户现在可以访问最新版本来升级其 Management Console。
5090189	UI - Management Console	Addressed a critical defect where users were unable to log in to the Vertica Management Console (MC) after upgrading from version 12.X to 25.4. Previously, users encountered 'invalid username and password' errors post-upgrade. This fix ensures that users can successfully authenticate and log in to the MC following an upgrade to version 25.4, restoring full access and functionality. 解决了从 12.X 升级到 25.4 后用户无法登录 Vertica Management Console（MC）的关键缺陷。此前，用户在升级后遇到「无效的用户名和密码」错误。此修复确保用户在升级到 25.4 后能够成功认证并登录 MC，恢复完全访问和功能。
5129004	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 导致某些查询返回截断的结果——未返回所有预期的行。此功能已被禁用，直至找到根本原因并修复。