Re: BUG #5702: pg fails to use a conditional index even the where clause matches the condition

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: Corin <info(at)netskin(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5702: pg fails to use a conditional index even the where clause matches the condition
Date: 2010-10-11 03:25:44
Message-ID: 2080.1286767544@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Jeff Davis <pgsql(at)j-davis(dot)com> writes:
> On Sat, 2010-10-09 at 23:28 +0000, Corin wrote:
>> I'd consider this a bug as "NOT x IS NULL" is the same as "x IS NOT NULL".

> That is false.

It's true for scalar input datatypes, though.

I had been wary of this idea because I didn't see any suitably cheap
place to insert the necessary processing, but after some reflection
and rejiggering of eval_const_expression's responsibilities, it's
done.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2010-10-11 04:13:41 Re: wrong timezone precision using plpythonu trigger
Previous Message Craig Ringer 2010-10-11 01:23:56 Re: BUG #5699: Postgres runs only under default user.