Re: [GENERAL] Bad plan when null is in an "in" list

2005-07-27 Thread Tom Lane
Jaime Casanova <[EMAIL PROTECTED]> writes: > On 7/26/05, Csaba Nagy <[EMAIL PROTECTED]> wrote: >> Seq Scan on big_table (cost=0.00..2447201.85 rows=448 width=16) >> Filter: ((bigint_col_2 = 12132131::bigint) OR NULL::boolean) >> >> Considering that NULL::boolean is always false, > null::boolean

Re: [GENERAL] Bad plan when null is in an "in" list

2005-07-27 Thread Jaime Casanova
On 7/26/05, Csaba Nagy <[EMAIL PROTECTED]> wrote: > Hi all, > > Jumping in directly to the subject, this is what I get: > > explain SELECT bigint_col_1, bigint_col_2 FROM big_table WHERE > bigint_col_2 in (12132131, null, null, null, > null); > > QUERY PLAN >

[GENERAL] Bad plan when null is in an "in" list

2005-07-26 Thread Csaba Nagy
Hi all, Jumping in directly to the subject, this is what I get: explain SELECT bigint_col_1, bigint_col_2 FROM big_table WHERE bigint_col_2 in (12132131, null, null, null, null); QUERY PLAN --- Seq Scan