On sön, 2010-10-31 at 10:39 -0400, Tom Lane wrote:
> To my mind, the reason we have a distinction between type OID and
> typmod
> is that for most operations, you know the type OID of the result but
> not the typmod. Trying to force typmod into every API that currently
> works with type OIDs isn't going to alter that, so the net result will
> just be a lot of inefficiency and extra notation to carry around
> "I don't know" markers.
This patch doesn't introduce typmods into places that didn't deal with
them before. It only replaces function calls and structures that had
separate arguments/fields for type OID and typmod with a single
argument/field.
