X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id B1BF5D1B170 for ; Fri, 18 Jun 2004 02:15:55 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 66633-08 for ; Fri, 18 Jun 2004 05:15:42 +0000 (GMT) Received: from trade-india.com (unknown [61.16.154.82]) by svr1.postgresql.org (Postfix) with SMTP id A9F91D1B272 for ; Fri, 18 Jun 2004 02:15:32 -0300 (ADT) Received: (qmail 5422 invoked from network); 18 Jun 2004 04:58:45 -0000 Received: from system100.trade-india-local.com (HELO ?192.168.0.100?) (192.168.0.100) by system66.trade-india-local.com with SMTP; 18 Jun 2004 04:58:45 -0000 Message-ID: <40D27AB0.5090303@trade-india.com> Date: Fri, 18 Jun 2004 10:46:32 +0530 From: Rajesh Kumar Mallah User-Agent: Mozilla Thunderbird 0.6 (X11/20040502) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: pgsql-admin@postgresql.org Subject: Re: weired behavior... after pg_resetxlog-> dump->initdb-->reload. References: <40CFFC68.5090704@trade-india.com> <21524.1087394109@sss.pgh.pa.us> <40D06096.90200@trade-india.com> <22477.1087400110@sss.pgh.pa.us> <40D06D1E.5000803@trade-india.com> <23874.1087409853@sss.pgh.pa.us> <40D1136F.3040708@trade-india.com> <12327.1087479361@sss.pgh.pa.us> In-Reply-To: <12327.1087479361@sss.pgh.pa.us> Content-Type: multipart/alternative; boundary="------------010508010603040603050205" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.4 tagged_above=0.0 required=5.0 tests=HTML_30_40, HTML_MESSAGE, HTML_TITLE_EMPTY X-Spam-Level: * X-Archive-Number: 200406/228 X-Sequence-Number: 13888 This is a multi-part message in MIME format. --------------010508010603040603050205 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Tom Lane wrote: >Rajesh Kumar Mallah 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? > name | character varying(120) | not null > If it's a text >type, what database encoding and locale settings (LC_COLLATE/LC_CTYPE) >are you using? > List of databases +-----------------+----------+-----------+ | Name | Owner | Encoding | +-----------------+----------+-----------+ | bric | postgres | UNICODE | +--------------------------------+-----------------+ | name | setting | +--------------------------------+-----------------+ | lc_collate | en_US.UTF-8 | | lc_ctype | en_US.UTF-8 | | lc_messages | en_US.iso885915 | | lc_monetary | en_US.iso885915 | | lc_numeric | en_US.iso885915 | | lc_time | en_US.iso885915 | > Can you investigate exactly what's stored within each >of these groups of matching names? > > Can you tell me how to do it please? > regards, tom lane > > > Regds Mallah. --------------010508010603040603050205 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Tom Lane wrote:
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?

name                  | character varying(120)   | not null
  If it's a text
type, what database encoding and locale settings (LC_COLLATE/LC_CTYPE)
are you using? 

 List of databases
+-----------------+----------+-----------+
|      Name       |  Owner   | Encoding  |
+-----------------+----------+-----------+
| bric            | postgres | UNICODE   |

+--------------------------------+-----------------+
|              name              |     setting     |
+--------------------------------+-----------------+
| lc_collate                     | en_US.UTF-8     |
| lc_ctype                       | en_US.UTF-8     |
| lc_messages                    | en_US.iso885915 |
| lc_monetary                    | en_US.iso885915 |
| lc_numeric                     | en_US.iso885915 |
| lc_time                        | en_US.iso885915 |


 Can you investigate exactly what's stored within each
of these groups of matching names?
  

Can you tell me how to do it please?
			regards, tom lane

  
Regds
Mallah.
--------------010508010603040603050205--