Re: BUG #14010: Multi-valued Index-only scans do not properly handle nulls in search - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #14010: Multi-valued Index-only scans do not properly handle nulls in search
Date
Msg-id 9408.1457550046@sss.pgh.pa.us
Whole thread Raw
In response to BUG #14010: Multi-valued Index-only scans do not properly handle nulls in search  (gtakahashi@palantir.com)
Responses Re: BUG #14010: Multi-valued Index-only scans do not properly handle nulls in search  (Glen Takahashi <gtakahashi@palantir.com>)
List pgsql-bugs
gtakahashi@palantir.com writes:
> select a,b from test_table where (a,b) > ('a','a') order by a,b;
> returns:
>  a | b
> ---+---
>  a | b
>  b | a
> (2 rows)

> create index on test_table (a,b);
> The same query now returns:
>  a | b
> ---+---
>  a | b
> (1 row)

Ugh.  This bug just passed its tenth birthday ... kind of astonishing
that nobody found it before.  Will fix, thanks for the report!

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #14008: corr, covar_pop function returns different values on the same dataset
Next
From: Tom Lane
Date:
Subject: Re: BUG #14010: Multi-valued Index-only scans do not properly handle nulls in search