| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
| Cc: | Alexandre Arruda <adaldeia(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: ERROR: found multixact from before relminmxid |
| Date: | 2018-04-09 21:23:56 |
| Message-ID: | CAH2-WznEitpnqh32LTwaEtuo54J-k3owtJ8nrnwvRK=aDoNfqA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Apr 9, 2018 at 7:01 AM, Tomas Vondra
<tomas(dot)vondra(at)2ndquadrant(dot)com> wrote:
> The bigger question is whether this can actually detect the issue. If
> it's due to an storage issue, then perhaps yes. But if you only see
> multixact issues consistently and nothing else, it might easily be a
> PostgreSQL bug (in which case the checksum will be correct).
You can also run amcheck. Get the version targeting earlier Postgres
releases off Github (there are packages for most Linux systems). This
can verify that the heap is consistent with indexes.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | karthik kumar | 2018-04-09 21:37:36 | Re: Fwd: Carto ODBC_FDW issue "ERROR: Connecting to driver" from PG to DB2 |
| Previous Message | Adrian Klaver | 2018-04-09 21:13:18 | Re: Fwd: Carto ODBC_FDW issue "ERROR: Connecting to driver" from PG to DB2 |