Peter Eisentraut <peter_e@gmx.net> writes:
> So while thinking about how to make this simpler I remembered the "distinct
> type" feature of SQL, which works quite similarly, namely the new type has
> the same structure as the old type, but is a separate entity. It looks like
> CREATE TYPE newtype AS oldtype;
> This feature by itself could be quite useful, and then we could simply add
> something like
> CREATE TYPE newtype AS oldtype WITH CASTS;
This seems like a great way to get lost in "ambiguous function" hell ...
regards, tom lane