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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: gtakahashi(at)palantir(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14010: Multi-valued Index-only scans do not properly handle nulls in search
Date: 2016-03-09 19:00:46
Message-ID: 9408.1457550046@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

gtakahashi(at)palantir(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Glen Takahashi 2016-03-09 19:51:19 Re: BUG #14010: Multi-valued Index-only scans do not properly handle nulls in search
Previous Message Tom Lane 2016-03-09 18:23:11 Re: BUG #14008: corr, covar_pop function returns different values on the same dataset