Re: Summary: changes needed in function defaults behavior

Tom Lane wrote:
> So to summarize what I think we agreed to yesterday:
>
> * CREATE OR REPLACE FUNCTION has to prevent reducing the pronargdefaults
> value of an existing function (ie, you can add more defaults but not
> remove any). This ensures a function that matched a given call before
> will continue to do so.
>
> * CREATE OR REPLACE FUNCTION also has to prevent a change in the actual
> datatype of the default for any polymorphic parameter. This ensures
> that we won't come to a different conclusion about the result type or
> the coerced type of any non-defaulted parameter.

I assume there will be some documentation explaining why these
restrictions exist because I am not sure it will be obvious.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +