Received: from gandalf.telecom.at (gandalf.telecom.at [194.118.26.84])
	by hub.org (8.9.3/8.9.3) with ESMTP id EAA01344
	for <hackers@postgresql.org>; Fri, 3 Sep 1999 04:01:05 -0400 (EDT)
	(envelope-from andreas.zeugswetter@telecom.at)
Received: from telecom.at (w0188000580.f000.d0188.sd.spardat.at
	[172.18.65.249])
	by gandalf.telecom.at (xxx/xxx) with ESMTP id KAA348146
	for <hackers@postgresql.org>; Fri, 3 Sep 1999 10:00:39 +0200
Message-ID: <37CF8025.588AD500@telecom.at>
Date: Fri, 03 Sep 1999 10:00:37 +0200
From: Andreas Zeugswetter <andreas.zeugswetter@telecom.at>
X-Mailer: Mozilla 4.61 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: hackers@postgresql.org
Subject: AW: [HACKERS] SELECT BUG 
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> But if it is correct, then we need to turn off oprcanhash for bpchareq.
> Odd that no one has noticed this before.

Currently it works for constants, because they are blank padded.
It does not work for the char(8) = char(16) comparison with two
table columns.

Eighter the hash function for bpchar itself should be trailing blank 
insensitive, or the bpchar would need to be padded or truncated before 
computing the hash.

Andreas