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

Re: Sequential Scan Index Bug

From: "Gabriel Weinberg" <yegg(at)alum(dot)mit(dot)edu>
To: "'Stephan Szabo'" <sszabo(at)megazone(dot)bigpanda(dot)com>
Cc: "'Bruno Wolff III'" <bruno(at)wolff(dot)to>, <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Sequential Scan Index Bug
Date: 2004-04-07 16:41:03
Message-ID: 001a01c41cbf$1e226b80$0900a8c0@yegg (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
Presumably, but that is not what I was doing.

I was taking a number from a user, which was supposed to be divisible by an
integer.  Sometimes the user left off the last digit when typing in the
number or otherwise typed it in wrong, rendering the input not divisible by
that number.

So it was looking for something like 4.345.


Gabriel Weinberg

-----Original Message-----
From: Stephan Szabo [mailto:sszabo(at)megazone(dot)bigpanda(dot)com] 
Sent: Wednesday, April 07, 2004 11:35 AM
To: Gabriel Weinberg
Cc: 'Bruno Wolff III'; pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] Sequential Scan Index Bug

On Wed, 7 Apr 2004, Gabriel Weinberg wrote:

> Yes, I thought I had done that, but now that I figured out what was 
> going on, I did it for all cases.  So it is no longer occurring for 
> me, but it still seems like a bug in PostgreSQL.  I would expect it to 
> throw an error immediately, instead of scanning the table for a value 
> of a different type.

But what if you said id = 4.0?  Would you want it to find the id=4 row?

In response to


pgsql-bugs by date

Next:From: Stephan SzaboDate: 2004-04-07 16:57:41
Subject: Re: Sequential Scan Index Bug
Previous:From: Stephan SzaboDate: 2004-04-07 15:35:02
Subject: Re: Sequential Scan Index Bug

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