Re: ERROR: posting list tuple with 20 items cannot be split at offset 168

Поиск
Список
Период
Сортировка
От Herman verschooten
Тема Re: ERROR: posting list tuple with 20 items cannot be split at offset 168
Дата
Msg-id 9B0DA07F-4022-4F1A-82B4-6FEC4F505B83@verschooten.net
обсуждение исходный текст
Ответ на Re: ERROR: posting list tuple with 20 items cannot be split at offset 168  (Andres Freund <andres@anarazel.de>)
Ответы Re: ERROR: posting list tuple with 20 items cannot be split at offset 168  (Peter Geoghegan <pg@bowt.ie>)
Список 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@anarazel.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




В списке pgsql-bugs по дате отправления:

Предыдущее
От: Kamigishi Rei
Дата:
Сообщение: Re: BUG #17245: Index corruption involving deduplicated entries
Следующее
От: PG Bug reporting form
Дата:
Сообщение: BUG #17256: Running pgagent on a custom user