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

INDEX broken on NUMERIC type.

From: mschout(at)gkg(dot)net
To: pgsql-bugs(at)postgreSQL(dot)org
Subject: INDEX broken on NUMERIC type.
Date: 1999-09-28 02:40:27
Message-ID: Pine.LNX.4.10.9909272138480.3140-100000@cdm-24-019.tca.net (view raw or flat)
Thread:
Lists: pgsql-bugs
============================================================================
                        POSTGRESQL BUG REPORT TEMPLATE
============================================================================


Your name		: Michael Schout
Your email address	: mschout(at)gkg(dot)net


System Configuration
---------------------
  Architecture (example: Intel Pentium)  	: Intel Pentium-II

  Operating System (example: Linux 2.0.26 ELF) 	: Linux 2.2.12 ELF

  PostgreSQL version (example: PostgreSQL-6.5.2): PostgreSQL-6.5.2 

  Compiler used (example:  gcc 2.8.0)		: gcc egcs-2.91.66


Please enter a FULL description of your problem:
------------------------------------------------

NUMERIC type cannot be used in an INDEX.

Please describe a way to repeat the problem.   Please try to provide a
concise reproducible example, if at all possible: 
----------------------------------------------------------------------

Method (1) using primary key syntax:
scdrought=> create table foo ( f1 NUMERIC(3,0) primary key );
NOTICE:  CREATE TABLE/PRIMARY KEY will create implicit index 'foo_pkey' for table 'foo'
ERROR:  Can't find a default operator class for type 1700.


Method (2) do it by hand.
mschout=> create table foo (f1 NUMERIC(3,0));
CREATE
mschout=> CREATE UNIQUE INDEX foo_pkey ON foo (f1);
ERROR:  Can't find a default operator class for type 1700.

If you know how this problem might be fixed, list the solution below:
---------------------------------------------------------------------


Responses

pgsql-bugs by date

Next:From: Bruce MomjianDate: 1999-09-28 03:20:54
Subject: Re: [BUGS] INDEX broken on NUMERIC type.
Previous:From: Tim NewellDate: 1999-09-27 15:12:04
Subject: Bug in index creation

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