Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA10770 for ; Thu, 18 May 2000 11:29:11 -0400 (EDT) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id LAA19588; Thu, 18 May 2000 11:28:37 -0400 (EDT) From: Bruce Momjian Message-Id: <200005181528.LAA19588@candle.pha.pa.us> Subject: Re: Re[2]: lower() for varchar data by creating an index In-Reply-To: <23453.958662047@sss.pgh.pa.us> from Tom Lane at "May 18, 2000 11:00:47 am" To: Tom Lane Date: Thu, 18 May 2000 11:28:37 -0400 (EDT) CC: gav , Mitch Vincent , pgsql-sql@postgresql.org X-Mailer: ELM [version 2.4ME+ PL72 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archive-Number: 200005/53 > 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? I would throw a notice and keep going. Should I commit the change? -- Bruce Momjian | http://www.op.net/~candle pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026