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

Is the fix for this one easy to apply? Would it be feasible for me to
backport and bring into PostgreSQL 9.3.6?
__________________________________________
Glen Takahashi | Palantir Technologies | gtakahashi(at)palantir(dot)com |
1.408.338.5065

On 3/9/16, 2:00 PM, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

>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