From: | Alex Pilosov <alex(at)pilosoft(dot)com> |
---|---|
To: | Per-Olof Pettersson <pgsql(at)peope(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Re: index doesn't work for null? |
Date: | 2001-05-16 00:42:22 |
Message-ID: | Pine.BSO.4.10.10105152041330.14362-100000@spider.pilosoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Sorry bout that. Actually query does 'is null', I made a mistake in
my post.
-alex
On Tue, 15 May 2001, Per-Olof Pettersson wrote:
> Hi Alex
>
> I have no idea if it is a known issue.
> Though "field=null" is not allowed in standard SQL.
> The correct statement should be "select from xx where field IS NULL;".
>
> Perhaps it will be handled better (or not).
>
> Best regards
> Per-Olof Pettersson
>
> >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
>
> On 2001-05-16, 00:21:34, alex(at)pilosoft(dot)com (Alex Pilosov) wrote regarding
> index doesn't work for null?:
>
>
> > I have a bit of a problem:
>
> > 'select from xx where field=null' will always result in seq scan even
> when
> > there's a [btree] index on the field.
>
> > Is this a known issue?
>
> > -alex
>
>
> > ---------------------------(end of broadcast)---------------------------
> > TIP 6: Have you searched our list archives?
>
> > http://www.postgresql.org/search.mpl
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | John Clark L. Naldoza | 2001-05-16 00:44:16 | Re: Not a PG question: SCSI question |
Previous Message | Albertson, Chris | 2001-05-15 23:54:27 | RE: Performance aggregates |