Re: weired behavior... after pg_resetxlog-> dump->initdb-->reload.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Rajesh Kumar Mallah <mallah(at)trade-india(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: weired behavior... after pg_resetxlog-> dump->initdb-->reload.
Date: 2004-06-17 13:36:01
Message-ID: 12327.1087479361@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Rajesh Kumar Mallah <mallah(at)trade-india(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Alessandro Meneguelli Coutinho 2004-06-17 13:59:52 Performance 7.3.4
Previous Message Harry 2004-06-17 12:59:17 initdb problem (Win2K Pro, cygwin)