Re: Re[2]: lower() for varchar data by creating an index

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: gav <gav(at)nlr(dot)ru>
Cc: "Mitch Vincent" <mitch(at)venux(dot)net>, pgsql-sql(at)postgresql(dot)org
Subject: Re: Re[2]: lower() for varchar data by creating an index
Date: 2000-05-18 15:00:47
Message-ID: 23453.958662047@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Alex Guryanow <gav(at)nlr(dot)ru> 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

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Bruce Momjian 2000-05-18 15:20:05 Re: Using substr with user defined types
Previous Message Tom Lane 2000-05-18 14:54:46 Re: Foreign keys and access privileges