Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA61540 for ; Thu, 18 May 2000 11:01:19 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id LAA23456; Thu, 18 May 2000 11:00:47 -0400 (EDT) To: gav cc: "Mitch Vincent" , pgsql-sql@postgresql.org Subject: Re: Re[2]: lower() for varchar data by creating an index In-reply-to: <5649.000518@nlr.ru> References: <00d901bfc00c$a3a36c00$4100000a@venux.net> <5649.000518@nlr.ru> Comments: In-reply-to Alex Guryanow message dated "Thu, 18 May 2000 15:34:53 +0400" Date: Thu, 18 May 2000 11:00:47 -0400 Message-ID: <23453.958662047@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200005/51 Alex Guryanow writes: > my-db=> DROP FUNCTION lower(varchar); > ERROR: RemoveFunction: function "lower" is built-in You can get rid of it by deleting the pg_proc tuple directly. I wonder though whether RemoveFunction isn't being overly protective --- is there any good reason not to allow people to delete built-in functions? Obviously you have only yourself to blame if you delete integer equals or something equally critical ;-) ... but there are a boatload of built-ins that are by no means critical. Comments anyone? regards, tom lane