Re: ERROR: posting list tuple with 20 items cannot be split at offset 168 - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: ERROR: posting list tuple with 20 items cannot be split at offset 168
Date
Msg-id CAH2-Wzmxq8oNkqMOoxYNbUUs+ZNGtC3foUi8z9D9xOMp0-8tog@mail.gmail.com
Whole thread Raw
In response to Re: ERROR: posting list tuple with 20 items cannot be split at offset 168  (Herman verschooten <Herman@verschooten.net>)
List pgsql-bugs
On Fri, Oct 29, 2021 at 1:47 AM Herman verschooten
<Herman@verschooten.net> wrote:
> The filesystem is EXT4 on a Proxmox container using LVM-thin.
>
> I have to check, but I believe there may still be a complete backup of the instance.

Thanks for getting back about this.

A fix for this bug will appear in Postgres 14.1. In the meantime I
suggest that you avoid using parallel VACUUM. For example, any scripts
that run VACUUM could be temporarily changed to make sure that
parallelism won't be used. If the script says "vacuum my_table;", then
that could be changed to "vacuum (parallel 0) my_table;", for example.
Just until you can upgrade to the next point release.

-- 
Peter Geoghegan



pgsql-bugs by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: BUG #17268: Possible corruption in toast index after reindex index concurrently
Next
From: PG Bug reporting form
Date:
Subject: BUG #17271: Updating enum columns type fails when constraints exist