mirror of
https://github.com/postgres/postgres.git
synced 2025-09-02 04:21:28 +03:00
Fix netmask handling in inet_minmax_multi_ops
When calculating distance in brin_minmax_multi_distance_inet(), the netmask was applied incorrectly. This results in (seemingly) incorrect ordering of values, triggering an assert. For builds without asserts this is mostly harmless - we may merge other ranges, possibly resulting in slightly less efficient index. But it's still correct and the greedy algorithm doesn't guarantee optimality anyway. Backpatch to 14, where minmax-multi indexes were introduced. Reported by Dmitry Dolgov, investigation and fix by me. Reported-by: Dmitry Dolgov Backpatch-through: 14 Discussion: https://postgr.es/m/17774-c6f3e36dd4471e67@postgresql.org
This commit is contained in:
@@ -2364,14 +2364,14 @@ brin_minmax_multi_distance_inet(PG_FUNCTION_ARGS)
|
||||
unsigned char mask;
|
||||
int nbits;
|
||||
|
||||
nbits = lena - (i * 8);
|
||||
nbits = Max(0, lena - (i * 8));
|
||||
if (nbits < 8)
|
||||
{
|
||||
mask = (0xFF << (8 - nbits));
|
||||
addra[i] = (addra[i] & mask);
|
||||
}
|
||||
|
||||
nbits = lenb - (i * 8);
|
||||
nbits = Max(0, lenb - (i * 8));
|
||||
if (nbits < 8)
|
||||
{
|
||||
mask = (0xFF << (8 - nbits));
|
||||
|
Reference in New Issue
Block a user