"Jonah H. Harris" <[EMAIL PROTECTED]> writes: > The attached patch handles the simple case where a user wants to > increase the user-defined storage size of a variable length object, > such as VARCHAR or NUMERIC, without having to rebuild the table.
This makes some really quite unacceptable assumptions about the meaning and encoding of typmod; in fact I don't believe it's even correct for NUMERIC, which uses a two-field encoding in typmod. NUMERIC(18,2) to NUMERIC(20,0) cannot be a work-free conversion. Given the plans to allow user-defined types to have their own interpretation of typmod, you can't just blithely assume you know the semantics of a typmod change. I'm also wondering what's the point of comparing attbyval etc when you've already checked it's the same type OID. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings