public inbox for [email protected]  

help / color / mirror / Atom feed

From: José Antonio Morcillo Valenciano <[email protected]>
To: Álvaro Herrera <[email protected]>
Cc: [email protected]
Subject: Re: BUG #19414: Wrong rows returned by index scan on HASH-partitioned table with PRIMARY KEY (PostgreSQL 16.9)
Date: Tue, 24 Feb 2026 10:26:45 +0100
Message-ID: <CA+nR40nyF++Y9v6u6qrSGMmhH9FxzoN_d4NAMXQDtn5KCaqaWA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

Hi!

After upgrading we reindex all our databases, so I don't see it clear.
The difficulty here is finding a test case to work with.



El lun, 23 feb 2026 a las 21:27, Álvaro Herrera (<[email protected]>)
escribió:

> 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"
>
>
>

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 using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: BUG #19414: Wrong rows returned by index scan on HASH-partitioned table with PRIMARY KEY (PostgreSQL 16.9)
  In-Reply-To: <CA+nR40nyF++Y9v6u6qrSGMmhH9FxzoN_d4NAMXQDtn5KCaqaWA@mail.gmail.com>

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

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