Jan Urbański wrote:
> Tom Lane wrote:
>> 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.
>
> Right. Updated patch attached.
Thanks, committed.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com