Re: Another issue in default-values patch: defaults expanded too soon - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Another issue in default-values patch: defaults expanded too soon
Date
Msg-id 17701.1229471597@sss.pgh.pa.us
Whole thread Raw
In response to Re: Another issue in default-values patch: defaults expanded too soon  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: Another issue in default-values patch: defaults expanded too soon
List pgsql-hackers
Gregory Stark <stark@enterprisedb.com> writes:
> We could say that changing the type of a default argument for a polymorphic
> argument isn't allowed just like changing the return value.

The point I was trying to make is that allowing defaults for polymorphic
args at all is going to cause a very significant amount of work and
complication, of which enforcing the above check is just a small part.
I wanted to see a plausible use-case for it before expending that work.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Gregory Stark
Date:
Subject: Re: Another issue in default-values patch: defaults expanded too soon
Next
From: Tom Lane
Date:
Subject: Variadic parameters vs parameter defaults