Re: seq scan on indexed column - Mailing list pgsql-admin

From postgresql@fruru.com
Subject Re: seq scan on indexed column
Date
Msg-id Pine.LNX.4.44.0203142326180.24047-100000@perycles.unix.be.EU.org
Whole thread Raw
In response to seq scan on indexed column  ("Zhang, Anna" <azhang@verisign.com>)
List pgsql-admin
On Thu, 14 Mar 2002, Zhang, Anna wrote:

> gtld_analysis=# explain SELECT NETBLOCK_START
> gtld_analysis-# FROM GTLD_OWNER
> gtld_analysis-# WHERE NETBLOCK_START = -2147483648;

You might want to try the same query but with the constant integer
enclosed in single quotes.  I find that (at least for int8) this changes
the behaviour wrt index usage -- most probably due to automatic
typecasting in the postgresql SQL parser.

Hope this helps...
Tycho

--
Tycho Fruru            tycho.fruru@conostix.com
Users' impressions of different operating systems, expressed as emoticons:
Linux:   :)
Windows: XP



pgsql-admin by date:

Previous
From: "Gill, Jeffrey L"
Date:
Subject: separating out database files
Next
From: Mike Schiraldi
Date:
Subject: Index scans, seq scans