Re: Function with default value not replacing old definition of the function - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Function with default value not replacing old definition of the function
Date
Msg-id 10789.1229027032@sss.pgh.pa.us
Whole thread Raw
In response to Re: Function with default value not replacing old definition of the function  (Dimitri Fontaine <dfontaine@hi-media.com>)
Responses Re: Function with default value not replacing old definition of the function  (Dimitri Fontaine <dfontaine@hi-media.com>)
List pgsql-hackers
Dimitri Fontaine <dfontaine@hi-media.com> writes:
>> The sanest answer I can see is "so, don't do that".

> Is there any warning level message at CREATE FUNCTION time for the  
> user/dba to know he's doing something... border line, almost shooting  
> himself in the foot?

It's not that easy to produce a message that wouldn't be annoying noise.
In particular, it's hard to know whether functions in different schemas
would represent a problem or not.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Robert Haas"
Date:
Subject: Re: benchmarking the query planner
Next
From: Dimitri Fontaine
Date:
Subject: Re: Function with default value not replacing old definition of the function