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 17403.1229470087@sss.pgh.pa.us
Whole thread Raw
In response to Re: Another issue in default-values patch: defaults expanded too soon  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Another issue in default-values patch: defaults expanded too soon  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
Josh Berkus <josh@agliodbs.com> writes:
> Huh?  Shouldn't changing a function which a view depends on require a 
> rebuild of the view?

There is no such concept as "a rebuild of the view".

> That is, I think we should treat changing the defaults the same as we 
> would changing the number and type of parameters; it kicks off a 
> dependency check and requires a CASCADE.

Dream on ... there is no such facility in Postgres and we are not going
to build one in the 8.4 timeframe.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Another issue in default-values patch: defaults expanded too soon
Next
From: Gregory Stark
Date:
Subject: Re: Another issue in default-values patch: defaults expanded too soon