暂无图片
暂无图片
暂无图片
暂无图片
暂无图片
首页 / Vertica 23.4.x BUG 修复记录

Vertica 23.4.x BUG 修复记录

simonchiang 2024-08-13
167

23.4.0-13

Updated 09/17/2024

Issue Key Component Description
VER-95821 Execution Engine An error in expression analysis for REGEXP_SUBSTR would sometimes lead to a crash when that function was in the join condition.
This issue has been resolved.
REGEXP_SUBSTR 表达式分析中的错误有时会导致函数处于连接条件时崩溃。
此问题已解决。
VER-95836 UI - Management Console There was an issue caused by a problem with URL parsing during the redirect to Keycloak from the MC, where if the URL had special characters (|), the URL parsing failed with this symbol.
We have made the fix and written proper loggers’ messages.
从 MC 重定向到 Keycloak 时，URL 解析出现问题，如果 URL 包含特殊字符 (|)，则 URL 解析会因该符号而失败。
我们已修复此问题并写入正确的记录器消息。
VER-95964 Machine Learning There is a corner case where an orphan blob may remain in a session when the training of an ML model is cancelled.
This orphan blob could cause a crash if there was an attempt to train a model with the same name on the same session.
This issue has been resolved.
有一种特殊情况，即当取消 ML 模型的训练时，会话中可能会残留一个孤立 blob。
如果尝试在同一会话中训练同名模型，此孤立 blob 可能会导致崩溃。此问题已解决。
VER-96128 Security install_vertica will no longer prefer the system openssl library to the one shipped with Vertica on non-fips systems.
If you would like to use the system openssl library, delete the openssl libraries located at /opt/vertica/lib.
install_vertica 将不再优先选择系统 openssl 库，而是优先选择非 fips 系统上 Vertica 附带的库。
如果您想要使用系统 openssl 库，请删除位于 /opt/vertica/lib 的 openssl 库。
VER-96253 EON Previously, in certain cases when a cancel occurred during Vertica uploads to the communal storage, the node would crash.
This issue has now been resolved.
以前，在某些情况下，当 Vertica 上传到公共存储期间发生取消时，节点会崩溃。
此问题现已解决。

23.4.0-12

Updated 07/29/2024

Issue Key Component Description
VER-95551 Execution Engine An issue that caused a crash while using WITHIN GROUP () function with listagg has been fixed.
修复了在将 WITHIN GROUP () 函数与 listagg 结合使用时导致崩溃的问题。
VER-95663 Execution Engine Due to a bug in the numeric division code, users would get a wrong result when evaluating the mod operator on some numeric values with large precision.
This issue has been resolved.
由于数字除法代码中存在错误，用户在对某些精度较高的数值进行 mod 运算符求值时会得到错误的结果。
此问题已解决。

23.4.0-11

Updated 07/16/2024

Issue Key Component Description
VER-95198 Optimizer Under certain circumstances, partition statistics could be used in place of full table statistics, leading to suboptimal plans. This has been corrected.
在某些情况下，分区统计信息可能代替全表统计信息，从而导致计划不理想。
此问题已得到更正。
VER-95250 Optimizer FKPK Joins over projections with derived expressions would put PK input on the Inner side, even when it was much bigger than FK input, which resulted in worse performance in some scenarios.
The issue has been resolved.
使用派生表达式对投影进行 FKPK 连接会将 PK 输入放在内侧，即使它比 FK 输入大得多，这在某些情况下会导致性能下降。
此问题已得到解决。
VER-95318 ComplexTypes, Kafka Integration Loading JSON/Avro data with Kafka and Flex parsers into tables with many columns suffered from performance degradation.
The performance issue has been resolved.
使用 Kafka 和 Flex 解析器将 JSON/Avro 数据加载到具有许多列的表中会导致性能下降。
此性能问题已得到解决。

23.4.0-10

Updated 07/10/2024

Issue Key Component Description
VER-94331 Kafka Integration The vkconfig --refresh-interval option now functions properly. Setting it to one hour will refresh the lane worker every hour.
vkconfig --refresh-interval 选项现在可正常运行。将其设置为一小时将每小时刷新一次通道工作器。
VER-94571 Data load / COPY In rare cases, copying a JSON to a table using FJsonParser or KafkaJsonParser could cause the server to go down.
This issue has been resolved.
在极少数情况下，使用 FJsonParser 或 KafkaJsonParser 将 JSON 复制到表可能会导致服务器关闭。
此问题已解决。
VER-94598 FlexTable The copy of multiple JSON files to a Vertica table using fjsonparser() was causing the initiator node to go down.
This issue has been resolved.
使用 fjsonparser() 将多个 JSON 文件复制到 Vertica 表会导致启动器节点关闭。
此问题已解决。
VER-95105 Optimizer If ARGMAX_AGG and DISTINCT were both used in a query, an internal error was raised.
This issue has been resolved.
Now, this case raises an unsupported error message that includes a hint on how to rework the SQL query to avoid the error.
如果在查询中同时使用 ARGMAX_AGG 和 DISTINCT，则会引发内部错误。此问题已解决。
现在，这种情况会引发一条不受支持的错误消息，其中包含有关如何重新执行 SQL 查询以避免错误的提示。
VER-95110 Data load / COPY Vertica is now handling the null file and a null found case outside the JSON object with fjsonparser.
Vertica 现在使用 fjsonparser 处理 JSON 对象之外的空文件和空发现情况。

23.4.0-9

Updated 05/30/2024

Issue Key Component Description
VER-89631 UI - Management Console The HTTP Strict-Transport-Security (HSTS) response header was added to all MC responses.
This header informs the browser that you should access the site through HTTPS only,
and that the browser should automatically convert any HTTP connections to HTTPS.
所有 MC 响应都添加了 HTTP 严格传输安全 (HSTS) 响应标头。
此标头告知浏览器您只能通过 HTTPS 访问网站，并且浏览器应自动将所有 HTTP 连接转换为 HTTPS。
VER-91910 Optimizer When a node goes down in Eon mode, the buddy node that handles double duty did not adjust the resource calculation.
Now, the behavior is consistent with the Enterprise mode node-down scenario.
当节点在 Eon 模式下发生故障时，处理双重任务的伙伴节点不会调整资源计算。
现在，该行为与企业模式节点故障场景一致。
VER-92925 UI - Management Console Previously, upgrading the Management Console from version 12.0.4 to 23.3.0 could cause LDAP users to be incorrectly migrated, preventing users from logging in.
This issue has been resolved.
此前，将管理控制台从版本 12.0.4 升级到 23.3.0 可能会导致 LDAP 用户错误迁移，从而阻止用户登录。
此问题已得到解决。
VER-93925 Execution Engine Whether LIKE ANY / ALL read strings as UTF8 character sequences or binary byte arrays depended on whether the collation of the current locale was binary,
leading to incorrect results when reading multi-character UTF8 strings in binary-collated locales.
This has been resolved.
Now, LIKE ANY / ALL always reads UTF8 character sequences, regardless of the current locale’s collation.
LIKE ANY / ALL 是否将字符串读取为 UTF8 字符序列或二进制字节数组取决于当前语言环境的排序规则是否为二进制，
这导致在二进制排序语言环境中读取多字符 UTF8 字符串时出现错误结果。
此问题已解决。
现在，LIKE ANY / ALL 始终读取 UTF8 字符序列，而不管当前语言环境的排序规则如何。
VER-93933 Client Drivers - ODBC The Windows DSN configuration utility no longer sets vertica as the default
Starting with version 11.1, providing a value causes the ODBC driver to assume the connection is using Kerberos authentication and communicates to the server that it prefers to use that authentication method,
assuming that the user has a grant to a Kerberos authentication method.
The KerberosServiceName value might be set in earlier versions of Windows ODBC DSNs.
Clearing the value will resolve the issue.
This issue only applies to users who have a Kerberos authentication method granted with a lower priority than other authentication methods and use the DSN configuration utility to set up a DSN on Windows.
KerberosServiceName value when editing a DSN.
Starting with version 11.1, providing a value causes the ODBC driver to assume the connection is using Kerberos authentication and communicates to the server that it prefers to use that authentication method,
assuming that the user has a grant to a Kerberos authentication method.
The KerberosServiceName value might be set in earlier versions of Windows ODBC DSNs.
Clearing the value will resolve the issue.
This issue only applies to users who have a Kerberos authentication method granted with a lower priority than other authentication methods and use the DSN configuration utility to set up a DSN on Windows.
Windows DSN 配置实用程序不再将 vertica 设置为默认值 。
从版本 11.1 开始，提供一个值会导致 ODBC 驱动程序假定连接正在使用 Kerberos 身份验证，
并通知服务器它更喜欢使用该身份验证方法，假设用户已获得 Kerberos 身份验证方法的授权。
KerberosServiceName 值可能在早期版本的 Windows ODBC DSN 中设置。
清除该值将解决此问题。
此问题仅适用于具有比其他身份验证方法优先级更低的 Kerberos 身份验证方法并使用 DSN 配置实用程序在 Windows 上设置 DSN 的用户。
编辑 DSN 时的 KerberosServiceName 值。
从版本 11.1 开始，提供一个值会导致 ODBC 驱动程序假定连接正在使用 Kerberos 身份验证，
并通知服务器它更喜欢使用该身份验证方法，
假设用户已获得 Kerberos 身份验证方法的授权。
KerberosServiceName 值可能在早期版本的 Windows ODBC DSN 中设置。
清除该值将解决此问题。
此问题仅适用于具有比其他身份验证方法优先级更低的 Kerberos 身份验证方法并使用 DSN 配置实用程序在 Windows 上设置 DSN 的用户。
VER-94090 Basics Setting SlowEventsProfilingFreq to 0 caused a cluster failure.
This has been resolved.
将 SlowEventsProfilingFreq 设置为 0 会导致集群故障。
此问题已得到解决。
VER-94093 Catalog Engine As dc_catalog_refcounts is useful only for debugging purposes, it is disabled by default.
由于 dc_catalog_refcounts 仅用于调试目的，因此默认情况下它是被禁用的。
VER-94199 Depot The subcluster-level depot pin policy became the cluster-level policy after upgrading to version 23.4 or later.
This issue has been resolved.
For users already using version 23.4 or later, subcluster-level depot policies must be recreated.
升级到 23.4 或更高版本后，子集群级仓库固定策略变为集群级策略。
此问题已解决。
对于已使用 23.4 或更高版本的用户，必须重新创建子集群级仓库策略。
VER-94337 Depot Depot fetch used to call aws list request, now doesn’t.
Depot fetch 过去用于调用 aws list request，现在不行了。

23.4.0-8

Updated 05/03/2024

Issue Key Component Description
VER-92663 Scrutinize The scrutinize utility produces a tar file of the data it collects.
Previously, scrutinize could fail to create this tar file if it encountered a broken symbolic link.
This issue has been resolved, and the size of the tar file is now logged to scrutinize_collection.log.
scrutinize 实用程序会生成一个包含其收集的数据的 tar 文件。
以前，如果 scrutinize 遇到损坏的符号链接，则可能无法创建此 tar 文件。
此问题已得到解决，tar 文件的大小现在会记录到 scrutinize_collection.log 中。
VER-93194 Data load / COPY When the Avro parser would read a byte array that is at most 8 bytes long into a numeric-typed target,
it would only accept a single-word numeric as the target type.
This has been resolved;
now, the Avro parser supports reading short byte arrays into multi-word numeric targets.
当 Avro 解析器将长度最多为 8 个字节的字节数组读入数字类型的目标时，它只接受单字数字作为目标类型。
此问题已得到解决；
现在，Avro 解析器支持将短字节数组读入多字数字目标。
VER-93326 Execution Engine User-Defined Aggregates didn’t work with single distinct built-in aggregate in the same query when the input wasn’t sorted on grouping columns plus distinct aggregate column.
The issue has been resolved.
当输入未按分组列和不同的聚合列排序时，用户定义聚合无法与同一查询中的单个不同的内置聚合一起使用。
此问题已解决。
VER-93446 Backup/DR LocalStorageLocator did not implement the construct_new() method. When called, it fell back to the StorageLocation.construct_new() method,
which raised an error. This issue has been resolved.
LocalStorageLocator.construct_new() is now implemented.
LocalStorageLocator 未实现 construct_new() 方法。
调用时，它会回退到 StorageLocation.construct_new() 方法，从而引发错误。
此问题已解决。LocalStorageLocator.construct_new() 现已实现。

23.4.0-7

Updated 04/05/2024

Issue Key Component Description
VER-91793 Execution Engine In rare situations, a logic error in the execution engine “ABuffer” operator would lead to buffer overruns resulting in undefined behavior. 
This issue has been resolved.
在极少数情况下，执行引擎“ABuffer”运算符中的逻辑错误会导致缓冲区溢出，从而导致未定义的行为。
此问题已得到解决。
VER-92113 Catalog Engine Previously, syslog notifiers could cause the node to go down when attached to certain DC tables.
This issue has been resolved.
以前，系统日志通知程序在连接到某些 DC 表时可能会导致节点关闭。
此问题已得到解决。
VER-92187 Data load / COPY Loading JSON arrays into table columns having different case for JSON key and table column used to fail in some cases. The issue has been resolved.
在某些情况下，将 JSON 数组加载到 JSON 键和表列大小写不同的表列中会失败。
此问题已解决。
VER-92287 Sessions The ALTER USER statement could not set the idle timeout for a user to the default value, which is defined by the DefaultIdleSessionTimeout configuration parameter.
If the empty string was specified, the idle timeout was set to unlimited.
This issue has been resolved.
You can now set the idle timeout to the DefaultIdleSessionTimeout value by specifying ‘default’ in the ALTER USER statement.
ALTER USER 语句无法将用户的空闲超时设置为默认值，该值由 DefaultIdleSessionTimeout 配置参数定义。
如果指定了空字符串，则空闲超时将设置为无限制。此问题已解决。
现在，您可以通过在 ALTER USER 语句中指定“default”将空闲超时设置为 DefaultIdleSessionTimeout 值。
VER-92748 HTTP Changing the Vertica server certificate triggers an automatic restart of the built-in HTTPS server.
When this happened on a busy system, the nodes could sometimes go down.
The issue has been resolved.
更改 Vertica 服务器证书会触发内置 HTTPS 服务器的自动重启。
当这种情况发生在繁忙的系统上时，节点有时会关闭。
此问题已解决。
VER-92821 Data load / COPY In COPY, some missing error checks made it so certain invalid input could crash the database.
This has been resolved.
在 COPY 中，缺少一些错误检查，导致某些无效输入可能导致数据库崩溃。
此问题已得到解决。
VER-92927 Installation Program When you installed Vertica on RHEL 9 with the install_vertica script, there was a warning about a missing ] character.
This issue has been resolved.
使用 install_vertica 脚本在 RHEL 9 上安装 Vertica 时，出现缺少 ] 字符的警告。
此问题已解决。
VER-93251 EON, S3 Previously, FIPS-enabled databases crashed when Vertica accessed an S3 bucket.
This issue has been resolved.
以前，当 Vertica 访问 S3 存储桶时，启用 FIPS 的数据库会崩溃。此问题已解决。

23.4.0-6

Updated 03/06/2024

Issue Key Component Description
VER-92109 DDL - Projection When we would scan over a projection sorted by two columns (ORDER BY a,b) and materialize only the second one in the sort order (b),
we would mistakenly assume the scan is sorted by that column for the purposes of collecting column statistics.
This would lead to possible incorrect results when predicate analysis is enabled, and has now been resolved.
当我们扫描按两列排序的投影（ORDER BY a,b）并仅实现按排序顺序（b）排序的第二个投影时，
我们会错误地认为扫描是按该列排序的，以便收集列统计信息。
这可能会导致在启用谓词分析时出现不正确的结果，现在已解决。
VER-92165 Procedural Languages Previously, running certain types of queries inside a stored procedure could cause the database to go down.
This issue has been resolved.
以前，在存储过程内运行某些类型的查询可能会导致数据库崩溃。
此问题已得到解决。
VER-92494 Execution Engine When you executed a query that filtered data into a JOIN statement, the query processed incorrectly or returned an error.
This issue has been resolved.
当您执行将数据过滤到 JOIN 语句中的查询时，查询处理不正确或返回错误。此问题已解决。

23.4.0-5

Updated 02/14/2024

Issue Key Component Description
VER-92055 Procedural Languages Fixed memory leaks that could occur with certain stored procedures.
修复了某些存储过程可能发生的内存泄漏。
VER-92124 Optimizer Queries using the same views repeatedly would sometimes return errors if those views included WITH clauses.
The issue has been resolved.
如果这些视图包含 WITH 子句，则重复使用相同视图的查询有时会返回错误。
此问题已解决。

23.4.0-4

Updated 02/14/2024

Issue Key Component Description
VER-90105 Catalog Engine Queries now run correctly when the files of delete vectors are in different storage locations.
当删除向量的文件位于不同的存储位置时，查询现在可以正确运行。
VER-91234 Backup/DR On HDFS, vbr tried to delete storage files from the wrong fan-out directory.
This issue has been resolved.
在 HDFS 上，vbr 尝试从错误的扇出目录中删除存储文件。
此问题已解决。
VER-91477 Execution Engine Since Version 11.1SP1, in some cases, an optimization in the query plan caused queries running under Crunch Scaling mode of COMPUTE_OPTIMIZED to produce wrong results.
This issue has been fixed.
自版本 11.1SP1 起，在某些情况下，查询计划中的优化会导致在 COMPUTE_OPTIMIZED 的 Crunch Scaling 模式下运行的查询产生错误结果。
此问题已修复。
VER-91667 ResourceManager If the default resource pool, defined by the DefaultResourcePoolForUsers configuration parameter,
was set to a value other than ‘general’, the user’s view incorrectly reported the non-general resource pool as the default pool when the user didn’t have that non-general pool set in the profile.
This issue has been resolved.
The default pool in such cases is now correctly reported as ‘general’.
如果由 DefaultResourcePoolForUsers 配置参数定义的默认资源池设置为“general”以外的值，
则当用户未在配置文件中设置非通用资源池时，用户视图会错误地将非通用资源池报告为默认池。
此问题已解决。
现在，此类情况下的默认池会正确报告为“general”。
VER-91714 Optimizer Queries with identically looking predicates on different tables used in different subqueries where predicates have very different selectivity could result in bad query plans and worse performance due to incorrect estimates on those tables.
The issue has been resolved.
如果查询对不同的表使用相同的谓词，而这些子查询中的谓词具有非常不同的选择性，
则这些查询可能会导致查询计划不佳，并且由于对这些表的估计不正确而导致性能下降。
此问题已解决。
VER-91742 Execution Engine The NULLIF function would infer its output type based on only the first argument.
This led to type compatibility errors when the first argument was a small numeric type and the second argument was a much larger numeric type.
This has been resolved;
now, numeric NULLIF accounts for the types of both arguments when inferring its output type.
NULLIF 函数将仅根据第一个参数推断其输出类型。
当第一个参数是较小的数字类型而第二个参数是较大的数字类型时，这会导致类型兼容性错误。
此问题已得到解决；
现在，数字 NULLIF 在推断其输出类型时会考虑两个参数的类型。
VER-91818 Execution Engine Vertica’s execution engine pre-fetches data from disk to reduce wait time during query execution.
Memory for the pre-fetch buffers was not reserved with the resource manager,
and in some situations a pre-fetch buffer could grow to a large size and bloat the memory footprint of a query until it completed. 
Now queries will account for this pre-fetch memory in requests to the resource manager;
and several internal changes mitigate the long-term memory footprint of larger-than-average pre-fetch buffers.
Vertica 的执行引擎会从磁盘预取数据，以减少查询执行期间的等待时间。
资源管理器不会保留预取缓冲区的内存，在某些情况下，预取缓冲区可能会增长到很大，并使查询的内存占用膨胀，直到查询完成。
现在，查询将在对资源管理器的请求中考虑此预取内存；并且一些内部更改可减轻大于平均水平的预取缓冲区的长期内存占用。

23.4.0-3

Updated 01/23/2024

Issue Key Component Description
VER-90535 Optimizer Update statements with subqueries in SET clauses would sometimes return an error.
The issue has been resolved.
SET 子句中带有子查询的更新语句有时会返回错误。此问题已解决。
VER-91149 Data load / COPY The upgrade of the C++ AWS SDK in 12.0.2 caused Vertica to make repeated calls to the metadata server for IAM authentication, affecting performance when accessing S3.
Vertica now resets the timestamp to prevent excessive pulling.
12.0.2 中 C++ AWS SDK 的升级导致 Vertica 重复调用元数据服务器进行 IAM 身份验证，影响访问 S3 时的性能。
Vertica 现在会重置时间戳以防止过度拉取。
VER-91189 Optimizer In version 10.1, Vertica updated its execution engine to sample execution times and selectivity of query predicates and join predicates to run them in the most efficient order. 
This has been disruptive to users who wrote queries which depended on a certain evaluation order,
in particular that single-table predicates would be evaluated before join conditions. 
In particular, queries whose single-table predicates filter out data which would raise a coercion error at the join condition would sometimes raise an error after this change due to the join condition being evaluated first. 
Now we have improved this experience by ensuring that join conditions do not raise type coercion errors when they are evaluated before single-table predicates.
在 10.1 版中，Vertica 更新了其执行引擎，以对查询谓词和连接谓词的执行时间和选择性进行采样，以便以最有效的顺序运行它们。
这对编写依赖于特定评估顺序的查询的用户造成了干扰，特别是单表谓词会在连接条件之前进行评估。
特别是，由于首先评估连接条件，其单表谓词过滤掉在连接条件下会引发强制错误的数据的查询有时会在更改后引发错误。
现在，我们通过确保在单表谓词之前评估连接条件时不会引发类型强制错误来改善这种体验。
VER-91336 Data Export Previously, large (chunked) file uploads from Vertica to GCS (such as exports of Parquet to GCS) would fail if the uploaded files included a special character in their path.
This issue has been resolved.
以前，如果上传文件的路径中包含特殊字符，则从 Vertica 到 GCS 的大型（分块）文件上传（例如将 Parquet 导出到 GCS）会失败。
此问题已解决。
VER-91550 Execution Engine When a hash join on unique keys would spill, the value columns would sometimes have alignment issues between how the hash table was written and how it gets read by the spill code.
If these value columns were string types, this could lead to a crash.
This issue has been resolved.
当唯一键上的哈希连接发生溢出时，值列有时会在哈希表的写入方式和溢出代码的读取方式之间出现对齐问题。
如果这些值列是字符串类型，则可能会导致崩溃。此问题已解决。

23.4.0-2

Updated 12/19/2023

Issue Key Component Description
VER-89773 Execution Engine When casting a negative numeric value to an integer and the result of that cast would be 0, then we would incorrectly get an “out of range” error.
This has been resolved.
当将负数值转换为整数时，如果转换结果为 0，我们会错误地收到“超出范围”错误。
此问题已得到解决。
VER-89777 Security The following improvements have been made to LDAPLink:
LDAP synchronizations have been optimized and now are much faster for nested groups.
Query profiling now works with LDAP dryrun functions.
LDAPLink 已做出以下改进：LDAP 同步已优化，现在对于嵌套组来说速度更快。
查询分析现在可与 LDAP dryrun 函数配合使用。
VER-89780 Hadoop Previously ‘Get block locations’ events were missing from the dc_udfs_events table, now this is fixed.
以前，dc_udfs_events 表中缺少“获取块位置”事件，现在已修复。
VER-89781 Optimizer In some circumstances, a UNION query that grouped an expression that coerced a value to a common data type returned an error.
This issue has been resolved.
在某些情况下，将强制将值转换为通用数据类型的表达式分组的 UNION 查询会返回错误。
此问题已解决。
VER-89843 Data Collector If a notifier was set for some DC tables and then subsequently dropped, it still remained present in those DC table policies.
This could cause a very large number of messages in vertica.log and potential node crashes.
The issue was resolved by making “DROP NOTIFIER” support the CASCADE logic.
Without CASCADE, drop would fail for the notifiers still used by DC tables.
如果为某些 DC 表设置了通知程序，随后又将其删除，则该通知程序仍存在于这些 DC 表策略中。
这可能会导致 vertica.log 中出现大量消息，并可能导致节点崩溃。
通过使“DROP NOTIFIER”支持 CASCADE 逻辑，此问题已得到解决。
如果没有 CASCADE，则 DC 表仍在使用的通知程序的删除将失败。
VER-89907 Security Previously, when configuring a chain of certificates longer than a root CA certificate and a client certificate for internode TLS, the configuration would successfully be applied,
but cause the cluster to shut down.
This has been fixed.
以前，当配置比根 CA 证书和节点间 TLS 的客户端证书更长的证书链时，配置会成功应用，但会导致集群关闭。
此问题已得到修复。
VER-89986 Kafka Integration When a notifier was set for the NotifierErrors or NotifierStats Data collector (DC) tables, notifications sent with a Kafka notifier might cause a loop that produced an infinite stream of notifications.
This might result in severely degradated node performance.
This issue has been resolved.
Now, notifications are disabled for these DC tables, and any existing notifiers have been removed from these tables.
当为 NotifierErrors 或 NotifierStats 数据收集器 (DC) 表设置通知程序时，使用 Kafka 通知程序发送的通知可能会导致循环，从而产生无限的通知流。
这可能会导致节点性能严重下降。
此问题已解决。现在，这些 DC 表的通知已被禁用，并且所有现有通知程序都已从这些表中删除。
VER-90064 ComplexTypes, Data load / COPY A logic gap in the source code could lead to an infinite loop while loading complex arrays with thousands of elements, causing the DML statement to never complete.
This issue has been fixed.
源代码中的逻辑漏洞可能会导致在加载包含数千个元素的复杂数组时出现无限循环，从而导致 DML 语句永远无法完成。
此问题已得到修复。
VER-90089 Security In cases of intermittent network connectivity to an LDAP server, Vertica will now retry bind operations.
当与 LDAP 服务器的网络连接间歇性中断时，Vertica 现在将重试绑定操作。
VER-90856 Optimizer Create Table As Select statements with repeated occurrences of now() and similar functions were inserting incorrect results into the target table.
The issue has been fixed.
重复出现 now() 和类似函数的 Create Table As Select 语句会将错误的结果插入目标表。
此问题已修复。

23.4.0-1

Updated 11/01/2023

Issue Key Component Description
VER-89489 EON, Execution Engine A LIKE ANY or LIKE ALL expression with a non-constant pattern argument on the right-hand side of the expression sometimes resulted in a crash or incorrect internal error.
This issue has been resolved.
Now, this type of pattern argument results in a normal error.
如果 LIKE ANY 或 LIKE ALL 表达式的右侧带有非常量模式参数，有时会导致崩溃或不正确的内部错误。
此问题已得到解决。
现在，这种类型的模式参数会导致正常错误。
VER-89565 Tuple Mover When the node with the lowest OID became secondary (for example, during cluster demotion),
there might have been an increased number of deadlocks and timeouts due to Data Manipulation Language (DML) statements and internal Tuple Mover tasks.
This issue has been resolved.
当具有最低 OID 的节点成为次要节点时（例如，在集群降级期间），
由于数据操作语言 (DML) 语句和内部 Tuple Mover 任务，可能会出现更多死锁和超时。
此问题已解决。
VER-89888 Backup/DR Backups to S3 object storage and Google Cloud Storage failed and returned a “Temp path” error.
This issue has been resolved.
备份到 S3 对象存储和 Google Cloud Storage 失败并返回“临时路径”错误。
此问题已解决。
VER-89895 Catalog Engine During load planning, the EnableWithTempRelReuseLimit configuration parameter was temporarily set to 1.
This affected other sessions on the same node, and concurrent COPY commands might make this change permanent.
This issue has been resolved.
在负载规划期间，EnableWithTempRelReuseLimit 配置参数临时设置为 1。
这会影响同一节点上的其他会话，并发 COPY 命令可能会使此更改永久生效。
此问题已解决。

23.4.0-0

Updated 10/04/2023

Issue Key Component Description
VER-40945 Client Drivers - VSQL Previously, vsql -f would return 0 (success) even if it encountered an error.
vsql -f now properly reports errors if they occur.
On success, it continues to return 0.
On failure, it returns a non-zero error code that maps to the [standard Linux error codes for file access|https://man7.org/linux/man-pages/man3/errno.3.html].
以前，即使遇到错误，vsql -f 也会返回 0（成功）。
现在，如果发生错误，vsql -f 可以正确报告错误。
成功时，它继续返回 0。
失败时，它返回一个非零错误代码，该代码映射到 [文件访问的标准 Linux 错误代码|https://man7.org/linux/man-pages/man3/errno.3.html]。
VER-69918 Client Drivers - VSQL VSQL now returns a more detailed error message if it is disconnected from the server.
如果与服务器断开连接，VSQL 现在会返回更详细的错误消息。
VER-81199 Execution Engine Queries with large tables stopped the database because the indices that Vertica uses to navigate the tables consumed too much RAM.
This issue has been resolved, and now the indices use less RAM.
查询大型表会导致数据库停止运行，因为 Vertica 用于浏览表的索引消耗了过多的 RAM。
此问题已解决，现在索引消耗的 RAM 更少。
VER-82009 Client Drivers - ODBC Previously, the connection property FastCursorClose was set to false by default, which prevented you from canceling sqlfetch().
You had to set it to true with conn.addToConnString(“FastCursorClose=1”); to cancel requests.
FastCursorClose is now set to {{true}} by default.
以前，连接属性 FastCursorClose 默认设置为 false，这会阻止您取消 sqlfetch()。您必须使用 conn.addToConnString(“FastCursorClose=1”); 将其设置为 true 才能取消请求。FastCursorClose 现在默认设置为 {{true}}。
VER-84047 Procedural Languages Previously, calling a stored procedure with insufficient temporary disk space could cause the node to go down.
This has been fixed.
Stored procedures now produce a standard query error indicating that there is insufficient space.
以前，在临时磁盘空间不足的情况下调用存储过程可能会导致节点关闭。
此问题已得到修复。
存储过程现在会产生标准查询错误，指示空间不足。
VER-85340 SDK Previously, you could not compile Vertica UDx builds with GCC compiler version 13 and higher.
This issue has been resolved.
以前，您无法使用 GCC 编译器版本 13 及更高版本编译 Vertica UDx 版本。
此问题已得到解决。
VER-86100 Performance tests In some cases, the NVL2 function caused Vertica to crash when it returned an array type.
This issue has been resolved.
在某些情况下，NVL2 函数在返回数组类型时会导致 Vertica 崩溃。
此问题已解决。
VER-86690 Optimizer During the planning stage, updates on tables with thousands of columns using thousands of SET USING clauses took a long time.
Planning performance for these updates was improved.
在规划阶段，使用数千个 SET USING 子句对包含数千列的表进行更新需要很长时间。
这些更新的规划性能已得到改善。
VER-86714 Catalog Engine If you used CREATE PROJECTION to create a projection whose name conflicted with an existing projection’s name, there would be a ROLLBACK.
This issue has been resolved.
Now, CREATE PROJECTIONS appends suffixes (_v1, v2, etc.) to new projection names to avoid naming conflicts.
如果您使用 CREATE PROJECTION 创建的投影的名称与现有投影的名称冲突，则会出现 ROLLBACK。
此问题已得到解决。现在，CREATE PROJECTIONS 会将后缀（_v1、v2 等）附加到新投影名称，以避免命名冲突。
VER-86863 Catalog Engine Previously, when a cluster lost quorum and switched to read-only mode or stopped, some transaction commits in the queue might get processed.
However, due to the loss of quorum, these commits might not have been persisted.
These “transient transactions” were reported as successful, but they were lost when the cluster restarted.
Now, when Vertica detects a transient transaction, it issues a WARNING so you can diagnose the problem, and it creates an event in ACTIVE_EVENTS that describes what happened.
以前，当集群失去仲裁并切换到只读模式或停止时，队列中的某些事务提交可能会得到处理。
但是，由于仲裁丢失，这些提交可能未被持久化。
这些“临时事务”被报告为成功，但在集群重新启动时它们丢失了。
现在，当 Vertica 检测到临时事务时，它会发出警告，以便您可以诊断问题，并在 ACTIVE_EVENTS 中创建一个事件来描述发生了什么。
VER-87049 Optimizer In some cases, using SQL macros that return string types could result in core dumps.
The issue has been resolved.
在某些情况下，使用返回字符串类型的 SQL 宏可能会导致核心转储。此问题已解决。
VER-87075 ComplexTypes, Execution Engine The optimization that makes it so that EXPLODE on complex types only materializes fields that are needed in the query was not applied to the similar UNNEST function.
This has been resolved, and now UNNEST similarly prunes out unused fields from scans/loads.
优化使得复杂类型的 EXPLODE 仅实现查询中需要的字段，但该优化并未应用于类似的 UNNEST 函数。
此问题已得到解决，现在 UNNEST 会同样从扫描/加载中删除未使用的字段。
VER-87084 EON In rare circumstances, the automatic sync of catalog files to the communal storage stopped working on some nodes.
Users could still manually sync with sync_catalog().
The issue has been resolved.
在极少数情况下，目录文件到公共存储的自动同步在某些节点上停止工作。
用户仍然可以使用 sync_catalog() 手动同步。
此问题已解决。
VER-87158 Tuple Mover The Tuple Mover logged a large number of PURGE requests on a projection while another MERGEOUT job was running on the same projection.
This issue has been resolved.
当另一个 MERGEOUT 作业正在同一投影上运行时，Tuple Mover 在同一投影上记录了大量 PURGE 请求。
此问题已解决。
VER-87183 Optimizer Queries that contained a WITH query that was referred to more than once and also contained multiple distinct aggregates failed with a system error.
This issue has been resolved.
包含多次引用的 WITH 查询且包含多个不同聚合的查询因系统错误而失败。
此问题已解决。
VER-87229 Optimizer NOT LIKE ANY and NOT LIKE ALL are consistent with PostgreSQL now - the phrases LIKE, ILIKE, NOT LIKE, and NOT ILIKE are generally treated as operators in PostgreSQL syntax.
NOT LIKE ANY 和 NOT LIKE ALL 现在与 PostgreSQL 一致 - 短语 LIKE、ILIKE、NOT LIKE 和 NOT ILIKE 在 PostgreSQL 语法中通常被视为运算符。
VER-87361 ComplexTypes The flex and kafka parsers would erroneously not respect the parameter “reject_on_materialized_type_error” in cases where an array was too large for the target column, and no element was rejected. 
Previously, such values would always be rejected.
This has been corrected, and now if “reject_on_materialized_type_error” is false, those values will be set to NULL instead.
如果数组对于目标列来说太大，并且没有元素被拒绝，flex 和 kafka 解析器会错误地不遵守参数“reject_on_materialized_type_error”。
以前，这样的值总是会被拒绝。
这个问题已经得到纠正，现在如果“reject_on_materialized_type_error”为 false，这些值将被设置为 NULL。
VER-87445 Kafka Integration In some circumstances, there were long timeouts or the process might hang indefinitely when the KafkaAvroParser accessed the Avro Schema Registry.
This issue has been resolved.
在某些情况下，当 KafkaAvroParser 访问 Avro Schema Registry 时，会出现长时间超时或进程可能无限期挂起的情况。
此问题已得到解决。
VER-87537 Documentation, Installation Program Some characters did not render correctly when specific commands were copied and pasted from the documentation.
This issue has been resolved.
从文档中复制粘贴特定命令时，某些字符无法正确呈现。
此问题已解决。
VER-87574 Backup/DR When the database had multiple backup locations, vbr did not use the correct credentials, causing operations to fail.
This issue has been corrected.
当数据库有多个备份位置时，vbr 未使用正确的凭据，导致操作失败。
此问题已得到纠正。
VER-87647 Execution Engine When casting a NUMERIC type to an INTEGER type, the bounds of acceptable values were based on the NUMERIC(18, 0) type, not the INTEGER type.
This meant that valid 64-bit integers with 19 digits returned an error.
This issue has been resolved, and now casting a NUMERIC type to an INTEGER type uses the correct bounds for the INTEGER type.
将 NUMERIC 类型转换为 INTEGER 类型时，可接受值的界限基于 NUMERIC(18, 0) 类型，而不是 INTEGER 类型。
这意味着有效的 64 位整数（19 位）会返回错误。
此问题已解决，现在将 NUMERIC 类型转换为 INTEGER 类型时会使用 INTEGER 类型的正确界限。
VER-87654 Admin Tools, Data Collector If you revived a database and the EnableDataCollector parameter was set to 1, you could not start the database after it was revived.
This issue was resolved.
To start the database, disable the cluster lease check.
如果您恢复了数据库并且 EnableDataCollector 参数设置为 1，则恢复后无法启动数据库。
此问题已解决。
要启动数据库，请禁用集群租约检查。
VER-87666 ComplexTypes, Execution Engine When rewriting a CROSS JOIN UNNEST query into an equivalent query that puts the UNNEST in a subquery,
requesting scalar columns from a table with larger complex columns could lead to an INTERNAL error.
This has been resolved.
将 CROSS JOIN UNNEST 查询重写为将 UNNEST 放在子查询中的等效查询时，
从具有较大复杂列的表中请求标量列可能会导致内部错误。此问题已解决。
VER-87668 Optimizer In some query plans with segmentation across multiple nodes,
Vertica would get an internal optimizer error when trying to prune out unused data edges from the plan.
This issue has been resolved.
在某些跨多个节点分段的查询计划中，Vertica 在尝试从计划中删去未使用的数据边缘时会出现内部优化器错误。
此问题已解决。
VER-87685 Client Drivers - ODBC Previously, the ODBC driver could return 64-bit FLOATs with incorrect values in its last bit,
which are not IEEE-compliant.
This has been fixed.
以前，ODBC 驱动程序可能会返回最后一位带有错误值的 64 位 FLOAT，这不符合 IEEE 标准。
此问题已得到修复。
VER-87701 Admin Tools On SUSE Linux Enterprise Server 15, the systemctl status verticad command failed.
This issue has been resolved.
在 SUSE Linux Enterprise Server 15 上，systemctl status verticad 命令失败。
此问题已解决。
VER-87723 Optimizer Queries with outer joins over subqueries with WHERE clauses that contain AND expressions with constant terms sometimes returned an error.
This issue has been resolved.
带有外连接的查询（包含带有常量项的 AND 表达式的 WHERE 子句）有时会返回错误。
此问题已解决。
VER-87817 Optimizer When you created a UDx side process, Vertica required that the current time zone have a name.
This caused a crash when a UDx side process was created under a time zone with a GMT offset rather than a name.
This issue has been resolved.
当您创建 UDx 端进程时，Vertica 要求当前时区具有名称。
当在具有 GMT 偏移量而非名称的时区下创建 UDx 端进程时，这会导致崩溃。
此问题已解决。
VER-87857 DevOps Fixed RPM digests by installing a newer version of the RPM on our build container when building RPMs.
通过在构建 RPM 时在我们的构建容器上安装较新版本的 RPM 来修复 RPM 摘要。
VER-87864 Procedural Languages Fixed memory leaks that could occur with certain stored procedures.
修复了某些存储过程可能发生的内存泄漏。
VER-87912 Procedural Languages When a Stored Procedure executed a subquery that included constraints, it returned an incorrect value.
This issue has been resolved.
当存储过程执行包含约束的子查询时，它会返回不正确的值。
此问题已解决。
VER-87942 EON The sync_catalog function failed when MinIO communal storage did not meet read-after-write and list-after-write consistency guarantees.
A check was added to bypass this restriction.
However, if possible, users should make sure that their MinIO storage is configured for read-after-write and list-after-write consistency.
当 MinIO 公共存储未满足“先读后写”和“先写后列表”一致性保证时，sync_catalog 函数会失败。
添加了检查以绕过此限制。
但是，如果可能，用户应确保其 MinIO 存储已配置为“先读后写”和“先写后列表”一致性。
VER-87945 Backup/DR Every time Vertica tries to load a snapshot, it checks all the storage files.
The file check costs too much time and is not necessary to do it so often. T
his check is now disabled.
每次 Vertica 尝试加载快照时，它都会检查所有存储文件。
文件检查耗费太多时间，没有必要如此频繁地进行。
此检查现已禁用。
VER-87992 Data Collector In some environments the io_stats system view was empty.
The monitoring functionality has been improved with better detection of I/O devices.
在某些环境中，io_stats 系统视图为空。
监控功能已得到改进，可以更好地检测 I/O 设备。
VER-88010 Optimizer In some cases, when Vertica used an optimization to constant-fold a CASE expression in a query into one of its possible results, it would produce an internal error.
This issue has been resolved.
在某些情况下，当 Vertica 使用优化将查询中的 CASE 表达式常量折叠为其可能的结果之一时，会产生内部错误。
此问题已解决。
VER-88014 DevOps, UI - Agent On SUSE Linux Enterprise Server 15, systemd failed to start the agent process, which caused some Management Console actions to fail on nodes that ran SUSE 15.
This issue has been resolved.
在 SUSE Linux Enterprise Server 15 上，systemd 无法启动代理进程，这导致某些管理控制台操作在运行 SUSE 15 的节点上失败。
此问题已解决。
VER-88166 Backup/DR Backup and restore operations failed on FIPS-enabled systems.
This issue has been resolved.
在启用 FIPS 的系统上备份和恢复操作失败。
此问题已解决。
VER-88171 Admin Tools The Admintools stop_db command failed and returned an error that described active sessions prevented the shutdown.
This issue has been resolved, and now the stop_db command stops the database with no errors.
Admintools stop_db 命令失败并返回错误，描述活动会话阻止关闭。
此问题已解决，现在 stop_db 命令可以停止数据库且不会出现任何错误。
VER-88233 UI - Management Console When you provisioned a new database on Amazon Web Services, the operation failed.
This issue has been resolved.
在 Amazon Web Services 上配置新数据库时，操作失败。
此问题已解决。
VER-88395 Logging Previously, if writes failed because the disk was full, Vertica could go down.
This has been fixed.
以前，如果由于磁盘已满而导致写入失败，Vertica 可能会瘫痪。
此问题已得到修复。
VER-88447 Execution Engine If there are user-created system tables and IS_SYSTEM_TABLE is set to “true” when you upgrade to 23.3.0,
queries on some V_CATALOG system tables fail with an assertion error after you complete the upgrade.
如果在升级到 23.3.0 时存在用户创建的系统表并且 IS_SYSTEM_TABLE 设置为“true”，
则升级完成后，某些 V_CATALOG 系统表上的查询将失败并出现断言错误。
VER-88468 Optimizer In some circumstances, queries with outer joins or cross joins that also utilized Top-k projections caused a server error.
This issue has been resolved.
在某些情况下，使用 Top-k 投影的外连接或交叉连接的查询会导致服务器错误。此问题已解决。
VER-88618 Optimizer Queries that contained a WITH query that was referred to more than once, and also contained joins on tables with segmented projections and SELECT DISTINCT or LIMIT subqueries sometimes produced an incorrect result.
This issue has been resolved.
包含多次引用的 WITH 查询以及包含分段投影的表上的联接和 SELECT DISTINCT 或 LIMIT 子查询的查询有时会产生错误结果。
此问题已解决。
VER-88634 Spread Previously, if Vertica received unexpected UDP traffic from its client port, the node could go down.
This issue has been fixed.
以前，如果 Vertica 从其客户端端口收到意外的 UDP 流量，则节点可能会关闭。
此问题已修复。
VER-88895 Security The following improvements have been made to LDAPLink:
LDAP synchronizations have been optimized and now are much faster for nested groups.
Query profiling now works with LDAP dryrun functions.
LDAPLink 已做出以下改进：
LDAP 同步已优化，现在对于嵌套组来说速度更快。
查询分析现在可与 LDAP dryrun 函数配合使用。
VER-89273 Data load / COPY If a Parquet query or load were to be interrupted (such as by a LIMIT clause, exception during execution, or user cancellation) while the database has configuration parameter “ParquetColumnReaderSize” set to zero, then Vertica could crash. 
This issue has been fixed.
如果在数据库的配置参数“ParquetColumnReaderSize”设置为零的情况下，Parquet 查询或加载被中断（例如，由于 LIMIT 子句、执行期间出现异常或用户取消），则 Vertica 可能会崩溃。
此问题已修复。

二维码.png

vertica
最后修改时间：2024-09-19 13:51:07
「喜欢这篇文章，您的关注和赞赏是给作者最好的鼓励」
关注作者
【版权声明】本文为墨天轮用户原创内容，转载时必须标注文章的来源（墨天轮），文章链接，文章作者等基本信息，否则作者和墨天轮有权追究责任。如果您发现墨天轮中有涉嫌抄袭或者侵权的内容，欢迎发送邮件至：contact@modb.pro进行举报，并提供相关证据，一经查实，墨天轮将立刻删除相关内容。

文章被以下合辑收录

Vertica各版本BUG修复记录（共7篇）
Vertica各版本bug修复记录汇总

评论

目录
  • 23.4.0-13
  • 23.4.0-12
  • 23.4.0-11
  • 23.4.0-10
  • 23.4.0-9
  • 23.4.0-8
  • 23.4.0-7
  • 23.4.0-6
  • 23.4.0-5
  • 23.4.0-4
  • 23.4.0-3
  • 23.4.0-2
  • 23.4.0-1
  • 23.4.0-0