Josh Berkus <josh@agliodbs.com> writes:
> Incompatible table changes would still require manual drop and
> recreation, of course. But most table changes to a production database
> are adding fields or changing constraints, which in most cases won't
> break dependant views or functions.
... as indeed they don't. What's your point? The question here was
about whether the DB should try to guess the right behavior for a
datatype change in an existing column.
regards, tom lane