Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eA8J71s26674 for ; Wed, 8 Nov 2000 14:07:01 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id eA8J6Q503136; Wed, 8 Nov 2000 14:06:26 -0500 (EST) To: Forest Wilkinson cc: pgsql-sql@postgresql.org Subject: Re: how to index a numeric(12,2) column? In-reply-to: References: <22500.973640915@sss.pgh.pa.us> Comments: In-reply-to Forest Wilkinson message dated "Wed, 08 Nov 2000 10:49:33 -0800" Date: Wed, 08 Nov 2000 14:06:26 -0500 Message-ID: <3133.973710386@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200011/57 X-Sequence-Number: 88 Forest Wilkinson writes: > Sorry; I hit send before adding that information. I'm using postgres > 6.5.3 on i386 Red Hat 6.1. Time to update, then. > It allows me to create an index on a NUMERIC(12,2) field using the > int8_ops class, but I'm wondering if this might have some undesirable > hidden side effects. Yes, and they won't be too hidden either: it won't work :-( Current sources check for that sort of type mismatch, but 6.5 failed to do so. regards, tom lane