Hi Tomas
The records have a timestamp column so we do know the time they were
written. We didn't find any I/O issues that match that time but
unfortunately as it's been a while we are not confident with that finding.
> Are there any other corrupted indexes on the table?
That was one of my first
On 12/9/20 12:07 AM, Huan Ruan wrote:
> HI Alvaro
>
> Unfortunately those records were written a while ago and we no longer keep
> their WAL logs. Thanks for your help anyway.
>
Can you estimate when roughly the records were written? E.g. by using a
rough estimate of WAL or XIDs generated per da
HI Alvaro
Unfortunately those records were written a while ago and we no longer keep
their WAL logs. Thanks for your help anyway.
Huan
On Fri, 27 Nov 2020 at 08:40, Huan Ruan wrote:
> Thanks Alvaro for pointing me to pageinspect. I will give it a try and
>> report back. It might take a few day
>
> Thanks Alvaro for pointing me to pageinspect. I will give it a try and
> report back. It might take a few days. I knew this module but have never
> tried it before.
>
On 2020-Nov-26, Huan Ruan wrote:
> Hi All
>
> We cannot work out a reproducible case but we have a copy of the offending
> database. I was hoping to know
I think the way to debug this would be to see what WAL records have been
emitted for the index, using pageinspect to find the problem index
tu
Hi All
We have a table with 623 million records. It appears a BRIN index of this
table on a timestamp column is missing some records, as illustrated below
in a cut-down version with additional columns and indices omitted.
We cannot work out a reproducible case but we have a copy of the offending
