Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.20.0.1.32\))
Subject: Re: ERROR: posting list tuple with 20 items cannot be split at offset
 168
From: Herman verschooten <Herman@verschooten.net>
In-Reply-To: 
 <CAH2-Wzmpz4=hv_hNcFv=2n==mqd1EK14wct_xNaT9YhEy7J1nw@mail.gmail.com>
Date: Tue, 26 Oct 2021 07:35:18 +0200
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>,
 Christl Nagels <christel.nagels@tranna.be>
Content-Transfer-Encoding: quoted-printable
Message-Id: <4F70DF51-FD72-41EC-9D7F-40C359AB3838@verschooten.net>
References: <8CDB73C1-E3AF-40A6-BA81-8AFE174C6402@verschooten.net>
 <CAH2-Wzmpz4=hv_hNcFv=2n==mqd1EK14wct_xNaT9YhEy7J1nw@mail.gmail.com>
To: Peter Geoghegan <pg@bowt.ie>
Archived-At: 
 <https://www.postgresql.org/message-id/4F70DF51-FD72-41EC-9D7F-40C359AB3838%40verschooten.net>
Precedence: bulk

Hi Peter,

Thanks for the info.
I don=E2=80=99t recall the exact 13 version we were on.

I can confirm that after dropping and recreating the 6 indexes =
everything is working fine.

Thanks for all the help, both here and on slack,

Herman


> Op 25 okt. 2021, om 17:29 heeft Peter Geoghegan <pg@bowt.ie> het =
volgende geschreven:
>=20
> On Mon, Oct 25, 2021 at 2:59 AM Herman verschooten
> <Herman@verschooten.net> wrote:
>> tranman_production=3D# update freights set cmr_received=3Dfalse where =
id=3D49632;
>> ERROR:  XX000: posting list tuple with 20 items cannot be split at =
offset 168
>> LOCATION:  _bt_swap_posting, nbtdedup.c:1037
>>=20
>> If I drop the index index_freights_on_cmr_received, then the update =
succeeds.
>=20
> What you see here is a defensive "can't happen" error that I added in
> commit 8f72bbac, and backpatched to Postgres 13.4, which came out on
> 2021-08-12. The goal of that error is to make a possible hard crash
> due to corruption into a slightly friendlier kind of failure (the
> error that you see here). Were you running 13.4 before the upgrade?
>=20
> If you were on 13.3 or earlier before the upgrade to 14, then it's
> possible that the problem was there all along, but is only now visible
> for the first time.
>=20
> --=20
> Peter Geoghegan