Received: from merganser.its.uu.se (merganser.its.uu.se [130.238.6.236]) by hub.org (8.9.3/8.9.3) with ESMTP id NAA70335 for ; Fri, 19 May 2000 13:35:43 -0400 (EDT) (envelope-from peter@localhost.its.uu.se) Received: from regulus.student.UU.SE ([130.238.5.2]:62318 "EHLO regulus.its.uu.se") by merganser.its.uu.se with ESMTP id ; Fri, 19 May 2000 19:34:32 +0200 Received: from peter (helo=localhost) by regulus.its.uu.se with local-esmtp (Exim 3.02 #2) id 12sqkM-0000Ld-00; Fri, 19 May 2000 19:39:38 +0200 Date: Fri, 19 May 2000 19:39:38 +0200 (CEST) From: Peter Eisentraut To: Tom Lane cc: Bruce Momjian , gav , Mitch Vincent , pgsql-sql@postgresql.org Subject: Re: Re[2]: lower() for varchar data by creating an index In-Reply-To: <23678.958664512@sss.pgh.pa.us> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-Archive-Number: 200005/84 Tom Lane writes: > 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. I'd have to agree. > 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. You might be referring to pg_shadow.usecatupd, but that only covers direct catalog updates. The postgres -O switch allows system schema changes, that doesn't apply either. Anyway, shouldn't you be able to do CREATE FUNCTION xxx (...) LANGUAGE 'internal'; to recreate it? (And that wouldn't actually require things like oideq to be in pg_proc, would it?) -- Peter Eisentraut Sernanders väg 10:115 peter_e@gmx.net 75262 Uppsala http://yi.org/peter-e/ Sweden