Re: BUG #6278: Index scans on '>' condition on field with many NULLS

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Maksym Boguk <maxim(dot)boguk(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6278: Index scans on '>' condition on field with many NULLS
Date: 2011-10-31 18:41:00
Message-ID: CA+TgmoaX-qvBRM1BLPkYsLtDbw2m5OfA=T8rQkLbMSc4KayaSg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Oct 31, 2011 at 12:43 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> A patch along these lines should be pretty localized.  Has anyone
> got an opinion on whether to back-patch or not?  This seems like a
> performance bug, but given the lack of prior complaints, maybe we
> shouldn't take any risks for it.

I think my vote would be to just fix it in master.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alexander 2011-10-31 18:46:42 Hanging with pg_restore and large objects
Previous Message Pavel Golub 2011-10-31 17:30:12 Re: BUG #6279: quoting needed for column name with non ascii chars