| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Herman verschooten <Herman(at)verschooten(dot)net> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Christl Nagels <christel(dot)nagels(at)tranna(dot)be> |
| Subject: | Re: ERROR: posting list tuple with 20 items cannot be split at offset 168 |
| Date: | 2021-11-04 01:21:02 |
| Message-ID: | CAH2-Wzmxq8oNkqMOoxYNbUUs+ZNGtC3foUi8z9D9xOMp0-8tog@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Oct 29, 2021 at 1:47 AM Herman verschooten
<Herman(at)verschooten(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2021-11-04 13:42:00 | BUG #17271: Updating enum columns type fails when constraints exist |
| Previous Message | Peter Geoghegan | 2021-11-04 01:07:27 | Re: BUG #17268: Possible corruption in toast index after reindex index concurrently |