Feedback-ID: ie3de48e3:Fastmail
Date: Mon, 23 Feb 2026 21:23:25 +0100
From: =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de>
To: jose.morcillo.valenciano@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19414: Wrong rows returned by index scan on
 HASH-partitioned table with PRIMARY KEY (PostgreSQL 16.9)
Message-ID: <202602232020.e2fyql4ip6hd@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <19414-add8251d7863a802@postgresql.org>
Archived-At: <https://www.postgresql.org/message-id/202602232020.e2fyql4ip6hd%40alvherre.pgsql>
Precedence: bulk

On 2026-Feb-19, PG Bug reporting form wrote:

> CREATE TABLE r_has_stock (
>     site_public_id varchar(10) NOT NULL,
[...]
> ) PARTITION BY HASH (site_public_id);
[...]
> Additional notes
>         •       Database collation: en_US.UTF-8
>         •       Server encoding: UTF8
>         •       Explicit casts and COLLATE tests did not change behaviour.
>         •       Issue appears only when index scan is used.
>         •       Table and indexes originate from a cluster initially running
> PostgreSQL 14.12 and later upgraded to 16.9.
>         •       After reindex the issue was resolved.
> 
> 
> Question
> 
> Could this be related to HASH partitioning combined with PRIMARY KEY /
> UNIQUE indexes, or to data created in older PostgreSQL versions and later
> upgraded?

I would be pretty certain that the problem is related to collation
changes, since the partition key is varchar and you said the problem
disappeared after the reindex.

The solution is exactly that: reindex any indexes potentially affected
by collation changes as part of a platform upgrade.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"No hay hombre que no aspire a la plenitud, es decir,
la suma de experiencias de que un hombre es capaz"