Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g1FIFPE44240 for ; Fri, 15 Feb 2002 13:15:25 -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.4/8.11.4) with ESMTP id g1FIFEf15112; Fri, 15 Feb 2002 13:15:14 -0500 (EST) To: "David Huselid" cc: wweng@kencast.com, pgsql-sql@postgresql.org Subject: Re: create index on function - why? In-reply-to: <004901c1b64a$c32e4870$9801a8c0@TELLURIUM> References: <004901c1b64a$c32e4870$9801a8c0@TELLURIUM> Comments: In-reply-to "David Huselid" message dated "Fri, 15 Feb 2002 13:01:15 -0500" Date: Fri, 15 Feb 2002 13:15:14 -0500 Message-ID: <15109.1013796914@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200202/186 X-Sequence-Number: 6612 "David Huselid" writes: > PostgreSQL 7.0.2 You need to update ... > But I am getting the following error: > ERROR: DefineIndex: function 'upper(varchar)' does not exist 7.0.* is quite picky about index functions; there has to be an exact match in pg_proc, not just a binary-compatible match. You could work around this by creating a pg_proc entry for upper(varchar) that matches the one for upper(text) ... but I'd suggest updating instead. regards, tom lane