Re: HASH index method not correctly handling NULL text

From: Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>
To: pgsql-general(at)postgresql(dot)org
Cc: david(dot)madore(at)ens(dot)fr
Subject: Re: HASH index method not correctly handling NULL text
Date: 2002-02-03 01:23:21
Message-ID: 1012699402.17741.39.camel@jiro
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sat, 2002-02-02 at 19:58, Tom Lane wrote:
> David Madore <david(dot)madore(at)ens(dot)fr> writes:
> > table has 345442 rows, of which 344339 have a non NULL value in the
> > column in question. The index creation proceeded without trouble, but
> > a subsequent "VACUUM VERBOSE ANALYZE" command gave the following
> > warning: "NUMBER OF INDEX' TUPLES (344339) IS NOT THE SAME AS HEAP'
> > (345442)" with the advice to recreate the index. Essentially, my
> > question is: is the warning incorrect or is the index so?
>
> The warning should be suppressed for hash indexes, since they don't
> include nulls. I believe this is fixed in 7.2.

Is there a reason why hash indexes don't include NULLs?

Cheers,

Neil

--
Neil Conway <neilconway(at)rogers(dot)com>
PGP Key ID: DB3C29FC

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2002-02-03 03:09:38 Re: HASH index method not correctly handling NULL text
Previous Message Jeff Martin 2002-02-03 01:09:21 Re: PostgreSQL transaction locking problem