citus/src/backend
Emel Şimşek e7a25d82c9
When creating a HTAB we need to use HASH_COMPARE flag in order to set a user defined comparison function. (#6845)
DESCRIPTION: Fixes memory errors, caught by valgrind, of type
"conditional jump or move depends on uninitialized value"

When running Citus tests under Postgres with valgrind, the test cases
calling into `NonBlockingShardSplit` function produce valgrind errors of
type "conditional jump or move depends on uninitialized value".

The issue is caused by creating a HTAB in a wrong way. HASH_COMPARE flag
should have been used when creating a HTAB with user defined comparison
function. In the absence of HASH_COMPARE flag, HTAB falls back into
built-in string comparison function. However, valgrind somehow discovers
that the match function is not assigned to the user defined function as
intended.

Fixes #6835
2023-04-11 21:24:33 +03:00
..
columnar Remove pg_depend entries from columnar metadata indexes to columnar-am 2023-03-14 17:13:52 +03:00
distributed When creating a HTAB we need to use HASH_COMPARE flag in order to set a user defined comparison function. (#6845) 2023-04-11 21:24:33 +03:00
.gitignore Initial commit of Citus 5.0 2016-02-11 04:05:32 +02:00