pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Herman verschooten <Herman@verschooten.net>
To: Peter Geoghegan <pg@bowt.ie>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Cc: Christl Nagels <christel.nagels@tranna.be>
Subject: Re: ERROR: posting list tuple with 20 items cannot be split at offset 168
Date: Tue, 26 Oct 2021 07:35:18 +0200
Message-ID: <4F70DF51-FD72-41EC-9D7F-40C359AB3838@verschooten.net> (raw)
In-Reply-To: <CAH2-Wzmpz4=hv_hNcFv=2n==mqd1EK14wct_xNaT9YhEy7J1nw@mail.gmail.com>
References: <8CDB73C1-E3AF-40A6-BA81-8AFE174C6402@verschooten.net>
	<CAH2-Wzmpz4=hv_hNcFv=2n==mqd1EK14wct_xNaT9YhEy7J1nw@mail.gmail.com>

Hi Peter,

Thanks for the info.
I don’t 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:
> 
> On Mon, Oct 25, 2021 at 2:59 AM Herman verschooten
> <Herman@verschooten.net> wrote:
>> tranman_production=# update freights set cmr_received=false where id=49632;
>> ERROR:  XX000: posting list tuple with 20 items cannot be split at offset 168
>> LOCATION:  _bt_swap_posting, nbtdedup.c:1037
>> 
>> If I drop the index index_freights_on_cmr_received, then the update succeeds.
> 
> 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?
> 
> 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.
> 
> -- 
> Peter Geoghegan






view thread (10+ messages)  latest in thread

Message-ID: <4F70DF51-FD72-41EC-9D7F-40C359AB3838@verschooten.net>
Permalink:  ../4F70DF51-FD72-41EC-9D7F-40C359AB3838@verschooten.net/
Also on:    postgresql.org/message-id/4F70DF51-FD72-41EC-9D7F-40C359AB3838@verschooten.net

 · 

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: pgsql-bugs@postgresql.org
  Cc: Herman@verschooten.net, pg@bowt.ie, pgsql-bugs@lists.postgresql.org, christel.nagels@tranna.be
  Subject: Re: ERROR: posting list tuple with 20 items cannot be split at offset 168
  In-Reply-To: <4F70DF51-FD72-41EC-9D7F-40C359AB3838@verschooten.net>

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

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