"Jonah H. Harris" <[EMAIL PROTECTED]> writes:

> On 10/26/06, Tom Lane <[EMAIL PROTECTED]> wrote:
>> This makes some really quite unacceptable assumptions about
>> the meaning and encoding of typmod ...
> True, so VARCHAR seems like the only one?  That's the only one I've
> really encountered in the field on a fairly regular basis.

I think what you want is to add a new method entry in pg_type to allow a type
to declare a method to tell you whether a change is work-free or not. Then any
type, even user-defined types, can allow some changes to be work-free and some
not without exposing any implementation details outside the type.

  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not

Reply via email to