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 LAA33006 for ; Thu, 18 May 2000 11:42:04 -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 LAA23681; Thu, 18 May 2000 11:41:53 -0400 (EDT) To: Bruce Momjian cc: gav , Mitch Vincent , pgsql-sql@postgresql.org Subject: Re: Re[2]: lower() for varchar data by creating an index In-reply-to: <200005181528.LAA19588@candle.pha.pa.us> References: <200005181528.LAA19588@candle.pha.pa.us> Comments: In-reply-to Bruce Momjian message dated "Thu, 18 May 2000 11:28:37 -0400" Date: Thu, 18 May 2000 11:41:52 -0400 Message-ID: <23678.958664512@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200005/54 Bruce Momjian writes: >> 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? What's the point of a notice? "You just deleted OID equals. Better luck with your next database." Either we think this is too dangerous to be allowed even to the dbadmin, or we don't. Actually, isn't there a backend switch that you have to set in order to do *really* dangerous stuff (DML operations on the system classes, for example)? Maybe the right answer is to allow deletion of builtin function entries only when that's set. But on third thought, it's a little silly to guard the pg_proc entries so carefully when we'll happily let the admin blow away the corresponding pg_operator entries. So I'd say just lose that error check completely... regards, tom lane