> > May be a plan could be to leave opaque, but throw a notice
> > when it is used in a create stmt, like:
> > NOTICE: the use of type OPAQUE should be avoided where possible
>
> Right, that's exactly the plan.
>
> Actually, I think we can tighten the use of OPAQUE quite a bit, too.
> The only supported uses will be (a) as an argument or result of a
> datatype's I/O function, (b) as the result of a trigger function.
In my paper I use C functions that take "any tuple".
I do not yet see how I can do that without opaque if we don't
have a "row" but only a "trigger" type.
Andreas
