Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uXdIj-00CO3L-1I for pgsql-general@arkaria.postgresql.org; Fri, 04 Jul 2025 10:05:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uXdIg-0005ti-94 for pgsql-general@arkaria.postgresql.org; Fri, 04 Jul 2025 10:05:46 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uXdIf-0005tX-UK for pgsql-general@lists.postgresql.org; Fri, 04 Jul 2025 10:05:46 +0000 Received: from mail-oi1-x22d.google.com ([2607:f8b0:4864:20::22d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uXdIe-005WLR-2e for pgsql-general@lists.postgresql.org; Fri, 04 Jul 2025 10:05:45 +0000 Received: by mail-oi1-x22d.google.com with SMTP id 5614622812f47-40a4de175a3so502964b6e.0 for ; Fri, 04 Jul 2025 03:05:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1751623544; x=1752228344; darn=lists.postgresql.org; h=cc:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=cT9gwxwsI+651B2tP8kKjntiGzAi0Ts9n4xf9AGMtQY=; b=Y4jVihC7GYVjhMKckXQQzdVt8uQXCqcyxseHx7ZyDE89EJsqqTxWP0caomLHyv8p/h /MQKMwJFMIV7I0nCJP+5zB1qWuXUt9u9iSacZpVeEMjVTbaz9hnJ++Z0l2nFxAQK5O8e Xxm9msMwFnd/iXcDNCxfLNq1/dS2UCdKguhP4g5ZGVftrB/j+nq7NrF90+fHocLn/Nfk Bx+asskmYZm1Jl+hrvWNzBFrq/vKu/hd/jhcml2Vle0lYkWYdcl3msSbiTLXoMQlmTbz KAKUqZLZ2UD4T/3U8+1G0IlrgkrPW1u1TNEQ7+T2pnxJzsiohTCq4dokHPLTJJVn/TJE wfgg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1751623544; x=1752228344; h=cc:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=cT9gwxwsI+651B2tP8kKjntiGzAi0Ts9n4xf9AGMtQY=; b=eyStzTvyrL/0qiIiAv4LUY1YZWXJPwmlI4wpBF3YOaF6ZeCzy4mdQ5qWjJFezP1Elh V3bPX3UEor9RhA4CC3K5bQLKjJl2TR949Y4Rk/DgdtVUmpaqgWDL+aJ3uQSUywnHWahr 2scfDXFwJN8qzplbImaohS0yv5X30DFzCc0IaqecrR2I9bFEkmbJ/aADIcsDwQvGq19T 0CDdzLdn24aP1PKs2ZJK16HHd/IoJd9tEvdVu9njyI9XGX4q4LiGdzIKh7t3rlVAh8BG /3mfcJQVWFMVtPcqS3UoTolEoyKK5m1JPnPw9sYynR3KFn4FBUiJToxXSr8qKABvwIUI 4+Qw== X-Gm-Message-State: AOJu0YwpfewWWTN494StC6kwA/WTQu7mXtqkGXTMjZaHhhtdNTpuGx79 xObaxKV4YzQkkXmHrLHked7Gi6ObOrl752/vNOEFKjC56gWygMcPfOhV6VTHI7CzcTpPASvemEt fsAPQRQwwvMDp6yQGsdTSTLbSwr+wRkZ01XyW X-Gm-Gg: ASbGncsElcwX84OW6D5bOiABRToNJBI3Z5vIHHte/TO4z5F30r40Rp3AwBJJcwLRO4W Kw18Qlx4LyBZr8WUox8xsVhikjdTCzjgKcYtOD8O7ivUc0Rs/QlKqOjTdAfBRd4Z4FDKdWtgoye fyKzFdV8Y/g4Iz7Sc71m8JNWEEE2fW8RMIP4hvc+k54YS6GzcEGxqxb5IjRPwa1vX0pAEmOTNcc kv4Ww== X-Google-Smtp-Source: AGHT+IFzrHgB7m37y2dWQ091CmqwhrZxRBas2Xx0yQrAAaO65IFVIfgK855187UFpzT9XKkmIdwkzpZvB4+W25deYQo= X-Received: by 2002:a05:6808:1a09:b0:40b:121b:865c with SMTP id 5614622812f47-40d04445a9fmr1398920b6e.36.1751623543828; Fri, 04 Jul 2025 03:05:43 -0700 (PDT) MIME-Version: 1.0 References: <6833523d-8e84-4749-952a-dcbfe9246d19@gmx.net> In-Reply-To: <6833523d-8e84-4749-952a-dcbfe9246d19@gmx.net> From: Ron Johnson Date: Fri, 4 Jul 2025 06:05:32 -0400 X-Gm-Features: Ac12FXxleMg6xpwT2zLQLyJw90Wn-qlcYXxuILgv8JqRTY81ee2zW-1uCG0Fi8s Message-ID: Subject: Re: Corrupt btree index includes rows that don't match Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000001c3708063917a3ba" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000001c3708063917a3ba Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Jul 4, 2025 at 5:50=E2=80=AFAM wrote: > > One coincidence is that we started seeing the first symptoms of this > > around the same time as libicu was updated with a security patch. > > However, postgres hasn=E2=80=99t been restarted and doesn=E2=80=99t ref= erence the > > new version in its process maps. Plus state groups are integers > > anyway. We also use the C locale, not ICU. > Sounds as if you are hit by locale changes: > > https://wiki.postgresql.org/wiki/Locale_data_changes > > > I think you will need to upgrade to prevent future problems like that: > > Postgres 15 introduced some mechanisms to track and validate version > discrepancies after an OS update. > > Postgres 17 added a "built-in" collation provider which is independent of > glibc > Why? Locale only cares about strings, and "Plus state groups are integers anyway." Besides, "We also use the C locale, not ICU." --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --0000000000001c3708063917a3ba Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Jul 4, 2025 at 5:50=E2=80=AFAM &l= t;shammat@gmx.net> wrote:
> One coincidence is that we started seeing the fi= rst symptoms of this
> around the same time as libicu was updated with a security patch.
> However, postgres hasn=E2=80=99t been restarted and doesn=E2=80=99t re= ference the
> new version in its process maps. Plus state groups are integers
> anyway. We also use the C locale, not ICU.
Sounds as if you are hit by locale changes:

https://wiki.postgresql.org/wiki/Locale_data_cha= nges


I think you will need to upgrade to prevent future problems like that:

Postgres 15 introduced some mechanisms to track and validate version discre= pancies after an OS update.

Postgres 17 added a "built-in" collation provider which is indepe= ndent of glibc

Why?=C2=A0 Locale only= cares about strings, and=C2=A0"Plus state groups are integers = anyway."

Besides,= "We also use the C locale, not ICU."

= --
Death to <Redacted>, and butter= sauce.
Don't boil me, I'm still alive.
<Redact= ed> lobster!
--0000000000001c3708063917a3ba--