From: | Herman verschooten <Herman(at)verschooten(dot)net> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | 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-10-29 08:47:34 |
Message-ID: | 9B0DA07F-4022-4F1A-82B4-6FEC4F505B83@verschooten.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hi,
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.
Herman
> Op 28 okt. 2021, om 23:47 heeft Andres Freund <andres(at)anarazel(dot)de> het volgende geschreven:
>
> Hi,
>
> On 2021-10-25 11:58:48 +0200, Herman verschooten wrote:
>> I upgraded postgres 13 to 14+231.pgdg18.04+1 during the weekend, virtual ubuntu 20.04.3.
>
> What filesystem is the postgres data stored on?
>
>
>> this morning a user reported an error when trying to change a flag in our web app (Phoenix, ecto).
>> I traced it back to an index issue on a boolean column.
>>
>> If I drop the index index_freights_on_cmr_received, then the update succeeds.
>>
>> If I recreate the index, the error resurfaces.
>
> Any chance you still have the WAL around from since the update? If we could
> scan the WAL to see what type of activity lead to the corruption, we might be
> able to narrow the cause down more easily.
>
> Greetings,
>
> Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2021-10-29 09:11:02 | BUG #17256: Running pgagent on a custom user |
Previous Message | Kamigishi Rei | 2021-10-29 08:17:49 | Re: BUG #17245: Index corruption involving deduplicated entries |