Re: BUG #6079: Wrong select result

Hello

It working as expected on 9.0.4 Linux. Please, can you recheck your
application? Try to use a console - psql,

postgres=3D# select * from foo where date_to is null and date_to > '2011-01=
-01';
 id | date_to
----+---------
(0 rows)

Regards

Pavel Stehule

2011/6/28 Renat <renat.nasyrov@itv.ru>:
>
> The following bug has been logged online:
>
> Bug reference: =C2=A0 =C2=A0 =C2=A06079
> Logged by: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Renat
> Email address: =C2=A0 =C2=A0 =C2=A0renat.nasyrov@itv.ru
> PostgreSQL version: 9.0.4
> Operating system: =C2=A0 Windows
> Description: =C2=A0 =C2=A0 =C2=A0 =C2=A0Wrong select result
> Details:
>
> INPUT:
>
> create table foo (
> id bigint not null,
> date_to timestamp without time zone,
> CONSTRAINT foo_pkey PRIMARY KEY (id)
> );
>
> CREATE INDEX foo_date_to_index
> =C2=A0ON foo
> =C2=A0USING btree
> =C2=A0(date_to)
>
> insert into foo (id, date_to) values (1, now());
> insert into foo (id, date_to) values (2, NULL);
>
> select * from foo where date_to is null and date_to > '2011-01-01'
>
> Expected: 0 rows
>
> But: it return 1 row with id=3D2
>
> If we will replace foo_date_to_index to:
>
> CREATE INDEX foo_date_to_index
> =C2=A0ON foo
> =C2=A0USING btree
> =C2=A0(date_to)
> =C2=A0WHERE date_to is NOT NULL
>
> Then:
>
> SELECT * FROM foo where date_to is null and date_to > '2011-01-01'
>
> Return: 0 rows
>
> Please explain for me what happens?
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
>