Hello,
We're looking into a problem with our application and have tracked it down
to index corruption, whereby we have many index rows pointing to the wrong
tuples in the heap.
Our table looks like:
```
Table "matrix.state_groups_state"
Column| Type | Collation | Nullable |
On Fri, 4 Jul 2025, 15:38 Ron Johnson, wrote:
> On Fri, Jul 4, 2025 at 9:49 AM Erik Johnston wrote:
>
>> Hi, a quick update:
>>
>> - We have discovered that the corruption was present from before libicu
>> update.
>> - We ran `pg_amcheck --index state_gr
when inserting a new row we sometimes add the
row to the index twice: once pointing from the correct state group to
the new row, and once from an old state group to the new row?
Thanks,
Erik
On 03/07/2025 18:07, Erik Johnston wrote:
Hello,
We're looking into a problem with our applicatio
re a bit mystified about how any
hardware failure could have caused such widespread damage to a single
index, whilst apparently leaving the rest of the database intact.
Any thoughts or suggestions are very much appreciated.
Thanks,
Erik
On 04/07/2025 15:59, Erik Johnston wrote:
On Fri, 4
