pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rajesh Kumar Mallah <mallah@trade-india.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: weired behavior... after pg_resetxlog-> dump->initdb-->reload.
Date: Fri, 18 Jun 2004 10:46:32 +0530
Message-ID: <40D27AB0.5090303@trade-india.com> (raw)
In-Reply-To: <12327.1087479361@sss.pgh.pa.us>
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>

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.

view thread (9+ messages)

Message-ID: <40D27AB0.5090303@trade-india.com>
Permalink:  ../40D27AB0.5090303@trade-india.com/
Also on:    postgresql.org/message-id/40D27AB0.5090303@trade-india.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: mallah@trade-india.com, tgl@sss.pgh.pa.us
  Subject: Re: weired behavior... after pg_resetxlog-> dump->initdb-->reload.
  In-Reply-To: <40D27AB0.5090303@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> <12327.1087479361@sss.pgh.pa.us> <40D27AB0.5090303@trade-india.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox