Re: Rule recompilation - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Rule recompilation
Date
Msg-id Pine.LNX.4.30.0107122147540.681-100000@peter.localdomain
Whole thread Raw
In response to Re: Rule recompilation  (Jan Wieck <JanWieck@Yahoo.com>)
List pgsql-hackers
Jan Wieck writes:

>     For most objects, there is no such "recompile" possible -  at
>     least  not  without  storing  alot more information than now.
>     Create a function and based on that  an  operator.  Then  you
>     drop  the  function and create another one. Hmmm, pg_operator
>     doesn't have the function name and argument  types,  it  only
>     knows the old functions oid. How do you find the new function
>     from here?

In these cases it'd be a lot simpler (and SQL-comforming) to implement the
DROP THING ... { RESTRICT | CASCADE } options.  This would probably catch
most honest user errors more cleanly than trying to automatically
recompile things that perhaps aren't even meant to fit together any
longer.

-- 
Peter Eisentraut   peter_e@gmx.net   http://funkturm.homeip.net/~peter



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Rule recompilation
Next
From: Tom Lane
Date:
Subject: Re: Rule recompilation