Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p1E99-0004kh-91 for pgsql-bugs@arkaria.postgresql.org; Fri, 02 Dec 2022 22:04:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1p1E97-00085M-RJ for pgsql-bugs@arkaria.postgresql.org; Fri, 02 Dec 2022 22:04:37 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p1E97-00083n-Iz for pgsql-bugs@lists.postgresql.org; Fri, 02 Dec 2022 22:04:37 +0000 Received: from mail-pf1-x42f.google.com ([2607:f8b0:4864:20::42f]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1p1E94-00009h-5U for pgsql-bugs@postgresql.org; Fri, 02 Dec 2022 22:04:36 +0000 Received: by mail-pf1-x42f.google.com with SMTP id l127so5485526pfl.2 for ; Fri, 02 Dec 2022 14:04:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=j-davis-com.20210112.gappssmtp.com; s=20210112; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:from:to:cc:subject :date:message-id:reply-to; bh=JNsZxb9H9bNNEf6XT1okj2XuhW6775emWMn6V0vUpyA=; b=5Uev6wbOkrIQ3ILXx1CS/iCvK2Xn2NcyA1YFRvqTMFoetUB/jrzMorNr0W4EaZMXFY tOrsK79gSh+s5jfbGb86kSmSt19hvLvlB55DdhaXz33Wej3+NEXRmtGWr+OISvZXaNxV VFqfwwsRLrbFGa6GafHC2MJEOi85jM9LQiryB2oecgQ+KyYU4QiJHLkTBKS2w6LQJm1w xxpywiDRZAtHRakakZdWsvw26XRLQ3B/sPupcsqJd+V+R/11qGQcthIi62xhMth57TX1 oElWSsrwzlWz/F/Z636tpT0U67v8C+uh9NmCiR36Kl9TZfeTH8LFcQpQFY/9G4koMeFy Lxww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=JNsZxb9H9bNNEf6XT1okj2XuhW6775emWMn6V0vUpyA=; b=u7QLYfYoEDDkdceters66EOTRV5aixinN9+27Ussvxlb3vJKbMLkd/Lx0wNldvahQm N34hDN7y4c08tr+V0NEH5IPe5NeDloRgZNcm6bpAbYDXLmE6Jhj7dOgT4petgdVNQIKH BZFWoWbgdEJ4MEPu5KbPfoiZrJbz15AyR4H9LPnSMYyT/dg8Tkc1DWJiBus3HxKuQu8M ITMQMXHvXloHtRTkrny/WshS5/mAsKi09iHjICPmhIOrH+HaN/U54CTBvud/WtMbb8Q8 sJiZSWrU1CU4p9qLHsxs62UZOqd8eK2UO8L+Jv72FnYZ5nx/QfrvJcTkIpryzQ96uLCc ESWw== X-Gm-Message-State: ANoB5pm6hiWw6f2EpbOhC00CFPv0TbyiB0uge2NMlB8FIBceQbPtB4iP RaPkU94byweEQiBjKTh7KrfLcw== X-Google-Smtp-Source: AA0mqf4SR8PEb+l9Xb8u6fuPfSRgJfS4wZr+qebYbz7/CFWoQtGIqFDBCwY4gPi1PIgT8VLcOU5glg== X-Received: by 2002:a62:62c4:0:b0:575:e44e:3e0 with SMTP id w187-20020a6262c4000000b00575e44e03e0mr14064732pfb.53.1670018671876; Fri, 02 Dec 2022 14:04:31 -0800 (PST) Received: from jeff-laptop.lan (c-73-231-146-4.hsd1.ca.comcast.net. [73.231.146.4]) by smtp.gmail.com with ESMTPSA id y1-20020aa79421000000b005765a5ff1fasm1954949pfo.213.2022.12.02.14.04.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 02 Dec 2022 14:04:31 -0800 (PST) Message-ID: <747aad52a232029184e675b7da23828ebcfd0658.camel@j-davis.com> Subject: Re: hashing bpchar for nondeterministic collations is broken From: Jeff Davis To: Tom Lane Cc: Richard Guo , pgsql-bugs@postgresql.org Date: Fri, 02 Dec 2022 14:04:30 -0800 In-Reply-To: <2137318.1670017756@sss.pgh.pa.us> References: <2137318.1670017756@sss.pgh.pa.us> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.44.4-0ubuntu1 MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, 2022-12-02 at 16:49 -0500, Tom Lane wrote: > Yeah.=C2=A0 Also, do we have this issue with hash indexes? No, it appears that hash indexes only call hashbpchar, which doesn't have the bug. Extended hash functions seem to only be used in hash partitioning, and other extended hash functions. Regards, Jeff Davis