Re: weired behavior... after pg_resetxlog-> dump->initdb-->reload. - Mailing list pgsql-admin

From Tom Lane
Subject Re: weired behavior... after pg_resetxlog-> dump->initdb-->reload.
Date
Msg-id 12327.1087479361@sss.pgh.pa.us
Whole thread Raw
In response to Re: weired behavior... after pg_resetxlog-> dump->initdb-->reload.  (Rajesh Kumar Mallah <mallah@trade-india.com>)
Responses Re: weired behavior... after pg_resetxlog-> dump->initdb-->reload.  (Rajesh Kumar Mallah <mallah@trade-india.com>)
List pgsql-admin
Rajesh Kumar Mallah <mallah@trade-india.com> writes:
> Yep the problem of original posting could be replicated on
> disabling hash aggregates. On disabling i could get the repeated rows.

Okay.  What I suspect is happening is that there are entries in the
column that are equal according to the datatype's comparison function,
but are not bitwise equal and therefore yield different hash codes.
This makes it a crapshoot whether they are seen to be equal or not
when hash aggregation is used.  We identified a similar bug in the
inet/cidr datatypes just a few weeks ago.

What exactly is the datatype of the "name" column?  If it's a text
type, what database encoding and locale settings (LC_COLLATE/LC_CTYPE)
are you using?  Can you investigate exactly what's stored within each
of these groups of matching names?

            regards, tom lane

pgsql-admin by date:

Previous
From: Bruno THOMAS
Date:
Subject: pg_class corrupted ?
Next
From: Alessandro Meneguelli Coutinho
Date:
Subject: Performance 7.3.4