From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Niles Oien <noien(at)nso(dot)edu> |
Cc: | PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: TOAST table repeatedly corrupted |
Date: | 2018-05-09 22:15:07 |
Message-ID: | CAH2-Wz=NhNb4oEPa8BjVME6HkFcFk-3b8nc_QPwyBsX8aE=j1Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, May 9, 2018 at 11:54 AM, Niles Oien <noien(at)nso(dot)edu> wrote:
> I think this is probably a bug? Every time it happens
> it affects the same table, hmi.rdvtrack_fd05. The hardware
> we're running on is fairly new, disks and memory are
> not throwing errors, and we've never had problems with any
> other tables. We're running on CentOS 6.8 - again, not brand
> new but hardly decrepit, either. I've rebuilt the table
> several times. This time I'd like to give the PG community
> a chance to chase it down before I do that.
amcheck could potentially reveal more information about the problem.
The version on Github works with 9.5, and there are Redhat/CentOS pgdg
packages you can use. See:
https://github.com/petergeoghegan/amcheck
The "heapallindexed" option may be of particular interest to you. It
verifies that the table has matching rows for a target index, in
addition to testing the structure of the target B-Tree index itself.
It doesn't do anything special with TOAST tables just yet, but it's
still the best general corruption test we have.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-05-09 22:46:04 | Re: TOAST table repeatedly corrupted |
Previous Message | Niles Oien | 2018-05-09 21:34:45 | Re: TOAST table repeatedly corrupted |