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 1uAxH2-004Vmk-G7 for pgsql-general@arkaria.postgresql.org; Fri, 02 May 2025 20:46:20 +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 1uAxH0-00BbCr-7K for pgsql-general@arkaria.postgresql.org; Fri, 02 May 2025 20:46:19 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uAxGz-00BbCi-Sz for pgsql-general@lists.postgresql.org; Fri, 02 May 2025 20:46:18 +0000 Received: from mail-oa1-x34.google.com ([2001:4860:4864:20::34]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uAxGz-000lFD-0Y for pgsql-general@postgresql.org; Fri, 02 May 2025 20:46:18 +0000 Received: by mail-oa1-x34.google.com with SMTP id 586e51a60fabf-2d4cefac09dso1417927fac.1 for ; Fri, 02 May 2025 13:46:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1746218775; x=1746823575; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=FN/SI2Fc8dQqHQwnm5GRdlab/irTcCJUIF+ImhRd29k=; b=LM2wG14PF9N0TFGiDLudBD+ZjY6CfwWY8iTSB0+iC5NVP6ssAY9+y7DkFx0IHHUqWe thoTar8YjOMpd8Y+ppZ1wNvRHcn1s5USvK5nnpndbTx9QBWr+UbMDmJ2J90RprkNr2nO I/rM2ScbRyII7Kz37Bc8lFG/Df7oqUvNBVT1ZZQwWTNEd/Y8yDAwX+i7FQ2vBh8n5Zbg /OtrIy6ZwzN98nC86Y/xZmnCT2m0cL4VXjjxecJNiSf3R9ABVZ+DPgb8Jo5jyLP2mjNZ 4j6Z9gY67ivbxcLdqXRRgk+midaNfCLTBw/RgKxuvjoKzMgGMuIX+dL4WXekz4AuwD4C xQ3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1746218775; x=1746823575; h=cc:to: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=FN/SI2Fc8dQqHQwnm5GRdlab/irTcCJUIF+ImhRd29k=; b=kvhzFXxWzs8klSy1fZjeQjIh6izcv6UJaxajDNcz0wHWedITL38Am1u9gIuOstF8Ko 3DsXikVwjh7fBjNez0ZLiQTiDTDOLRAt4uApuaaibrD1P07OeVomQKsZroDcKKJQRdKA Mt9Wup1r66gh2vQmdaK+LuAZVj5brIo4yqQ6deTdTMIFmE3+ue2E+tpzNkwNMwxdcYFN 2+qYNwCBkN87b12Jk2tC5rRNLKFF9S40eX05FL/1kX/jSmvbx3Qc0/Fc72NDnbAYHX87 qGss57gNS8hVMy9/JBcmmf0yhUK5LvLCl+GDVxXneqqVJPu4w710N5Ex7YV9TtpyjQQN rVZA== X-Gm-Message-State: AOJu0YzDayUxcs21CFsZlyRWzZ98UxFYWBHtCuLi75YifREwz85GWpmJ lckRaWhfs/xy382+OkGd/fA+Q6QGYnIhn/Ffz37PNmL7uFKG/DxR5buFu7xmu26aYXZ1lPC19i0 IuWsRM5HvOVB08vHBa7hliP+JnLY= X-Gm-Gg: ASbGncs5YimeRYafDIq6w+TD5Yve/fNXr+3HyrRfSDVfLNnZYhU32/Yg2MWxj4guWmU XWh2k2yOtV6CuZ1Qc2If69WYalSvm8DfvTlxGRV8a3sNvO8dg1+a3NUz9wP1emBrJRtLylTIUfD yoGn7mUKev4X76J83tuUfV X-Google-Smtp-Source: AGHT+IH6irZMjWg60M5j02W0YyYF6eCtNCUNbvX9EWdR7cPSXwphm+OwOs3BKEFSNWqlKwGJqSi3jpVhjnJnxLJqeog= X-Received: by 2002:a05:6871:7404:b0:2cc:3523:9cd5 with SMTP id 586e51a60fabf-2dab30a013fmr2150925fac.17.1746218775139; Fri, 02 May 2025 13:46:15 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "David G. Johnston" Date: Fri, 2 May 2025 13:45:38 -0700 X-Gm-Features: ATxdqUEMMBxbv6-t_iKrOWzPiGK4WWBZNYHtsHlLKGO6dbmJsZTbbeHvJ5j-W9Q Message-ID: Subject: Re: an error message that I don't understand To: Martin Mueller Cc: Postgres General Content-Type: multipart/alternative; boundary="000000000000cadafe06342d3dcc" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000cadafe06342d3dcc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, May 2, 2025 at 1:25=E2=80=AFPM Martin Mueller < martinmueller@northwestern.edu> wrote: > > table tid from new index tuple (32586,21) overlaps with invalid duplicate > tuple at offset 120 of block 4398 in index "aacorrections_tcpreading_idx" > Read that as "your index is corrupted". > I have no idea what is going on or how to deal with it and will be > grateful for advice > > > You will need to rebuild the index. If you've recently performed an OS upgrade you may also wish to update most/all indexes to fix possible collations issues. David J. --000000000000cadafe06342d3dcc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, May 2, 2025 at 1:25=E2=80=AFPM Martin Mueller <= martinmueller@northwester= n.edu> wrote:


table tid from new in= dex tuple (32586,21) overlaps with invalid duplicate tuple at offset 120 of= block 4398 in index "aacorrections_tcpreading_idx"


Read that as "your index= is corrupted".
=C2=A0

I have no idea what i= s going on or how to deal with it and will be grateful for advice=

=C2=A0<= /p>


You will need to rebuil= d the index.

If you've recently performed an OS up= grade you may also wish to update most/all indexes to fix possible collatio= ns issues.

David J.


--000000000000cadafe06342d3dcc--