"Heikki Linnakangas" <[EMAIL PROTECTED]> writes: > Jan UrbaÅski wrote: >> + * XXX or maybe fall back on attrtype-> stuff when these are NULL? That >> way >> + * we won't break other people's custom typanalyze functions. Not sure >> if >> + * any exist, though.
> I tried to google for a user defined data type with a custom typanalyze > function but didn't find anything, so I don't think it's an issue. Oh, it absolutely is an issue. PostGIS has them, if no one else does. I think the correct solution is to initialize the fields to match the column type before calling the typanalyze function. Then you don't break compatibility for existing typanalyze functions. It's also less code, since the standard typanalyze functions can rely on those preset values. regards, tom lane -- Sent via pgsql-patches mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-patches