Skip site navigation (1) Skip section navigation (2)

Re: Sequential Scan Index Bug

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Gabriel Weinberg <yegg(at)alum(dot)mit(dot)edu>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Sequential Scan Index Bug
Date: 2004-04-07 05:37:42
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
On Sat, Apr 03, 2004 at 13:51:56 -0500,
  Gabriel Weinberg <yegg(at)alum(dot)mit(dot)edu> wrote:
> I have a table with an integer column with about 10M rows in it.
> This column has an index (btree).
> When I try to select a row using this column with an integer, e.g. select *
> from table where id=4, it always uses the index.  However, if I select try
> to select a row using this column with a decimal, e.g. select * from table
> where id=4.343, it skips the index entirely and does a sequential scan of
> the table.
> I am using v7.4.2 on Freebsd 4.9.

Depending on what you want to do, you probably either want to cast the
value to an int explicitly or combine that with a test (using a stable
function) to make sure the number is actually an integer.

In response to


pgsql-bugs by date

Next:From: PostgreSQL Bugs ListDate: 2004-04-07 06:31:47
Subject: BUG #1129: select query returns multiple results for a japanese characters
Previous:From: Jiang WeiDate: 2004-04-07 00:56:14

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group