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 9113AD1B18F for ; Thu, 17 Jun 2004 10:36:15 -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 00877-04 for ; Thu, 17 Jun 2004 13:36:07 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id A0FDCD1B20E for ; Thu, 17 Jun 2004 10:36:00 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i5HDa1xI012328; Thu, 17 Jun 2004 09:36:03 -0400 (EDT) To: Rajesh Kumar Mallah Cc: pgsql-admin@postgresql.org Subject: Re: weired behavior... after pg_resetxlog-> dump->initdb-->reload. In-reply-to: <40D1136F.3040708@trade-india.com> 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> Comments: In-reply-to Rajesh Kumar Mallah message dated "Thu, 17 Jun 2004 09:13:43 +0530" Date: Thu, 17 Jun 2004 09:36:01 -0400 Message-ID: <12327.1087479361@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200406/219 X-Sequence-Number: 13879 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? 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