Re: pgsql: Fix netmask handling in inet_minmax_multi_ops

2023-03-26 Thread Tom Lane
Tomas Vondra writes: > On 3/20/23 10:28, Tomas Vondra wrote: >> Reported by Dmitry Dolgov, investigation and fix by me. >> Reported-by: Dmitry Dolgov > Correction - the issue was reported by Robins Tharakan, I got confused > while writing the commit message. I don't know if this issue is to be >

Re: pgsql: Fix netmask handling in inet_minmax_multi_ops

2023-03-26 Thread Tomas Vondra
On 3/20/23 10:28, Tomas Vondra wrote: > 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

pgsql: Fix netmask handling in inet_minmax_multi_ops

2023-03-20 Thread Tomas Vondra
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 othe

pgsql: Fix netmask handling in inet_minmax_multi_ops

2023-03-20 Thread Tomas Vondra
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 othe

pgsql: Fix netmask handling in inet_minmax_multi_ops

2023-03-20 Thread Tomas Vondra
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 othe