| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Daulat Ram <Daulat(dot)Ram(at)exponential(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: FATAL: SMgrRelation hashtable corrupted |
| Date: | 2019-05-17 17:09:22 |
| Message-ID: | 29772.1558112962@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> On 2019-May-17, Tom Lane wrote:
>> The good news is that the underlying ALTER TABLE bug is fixed in 11.3.
>> The bad news is that your database is probably toast anyway --- an update
>> won't undo the catalog corruption that is causing the WAL replay crash.
>> I hope you have a recent backup to restore from.
> Hmm, shouldn't it be possible to do a PITR restore to the point just
> before the problem record, ie. 5E/17061648?
If he's got the necessary WAL archives :-(
A dump and restore would be advisable afterwards in any case, since
the catalog corruption would still be there.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Will Hartung | 2019-05-17 19:10:24 | Loading table with indexed jsonb field is stalling |
| Previous Message | Alvaro Herrera | 2019-05-17 15:42:37 | Re: FATAL: SMgrRelation hashtable corrupted |