n for the week.
Yes this is the case, and in my case I wouldn't want to change the order.
Sure it would be nice to support this case too, but not if it implies
penalties for more typical queries. Doing the expansion manually isn't
that hard (but quite ugly).
Thanks for all answers.
Reg
From: Tomasz Myrta [mailto:[EMAIL PROTECTED]]
> I'm not sure unique index works properly for null values. I can't
> explain, why. Maybe it comes from SQL standard - null i a
> special value
Yeah, I thought about that too, but I think that behaviour is really bad and
would consider it a bug. The
1232132 AND b < 123123123213123
Postgres then behaved better and choosed the composite index in all three cases
resulting in a very large improvement...
Why is this, and has it been improved in more recent versions?
Thanks in advance,
Jimmy Mäkelä
