Re: extend VacAttrStats to allow stavalues of different types

From: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>
To: Jan Urbański <j(dot)urbanski(at)students(dot)mimuw(dot)edu(dot)pl>
Cc: "Postgres - Patches" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: extend VacAttrStats to allow stavalues of different types
Date: 2008-06-02 07:52:51
Message-ID: 4843A6D3.2040403@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Jan Urbański wrote:
> Following the conclusion here:
> http://archives.postgresql.org/pgsql-hackers/2008-05/msg00273.php
> here's a patch that extends VacAttrStats to allow typanalyze functions
> to store statistic values of different types than the underlying column.

Looks good to me at first glance.

About this comment:

> + * 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. It's
a bit nasty, though, because if one exists, it will compile and run just
fine, until you run ANALYZE. In general it's better to break an old API
obviously rather than silently, so that the old code doesn't even compile.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Dawid Kuroczko 2008-06-02 10:09:19 Re: [0/4] Proposal of SE-PostgreSQL patches
Previous Message daveg 2008-06-02 06:53:38 Re: Feature: give pg_dump a WHERE clause expression