| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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 15:34:16 |
| Message-ID: | 20190517153416.di2z2e5bijblojap@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
On 2019-05-17 09:30:05 -0400, 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.
Should there not be a backup, couldn't weaken the error checks during
replay a bit (locally), to allow replay to progress? The indexes will be
toast, but it ought to allow to recover the table data completely.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-05-17 15:42:37 | Re: FATAL: SMgrRelation hashtable corrupted |
| Previous Message | Tom Lane | 2019-05-17 13:30:05 | Re: FATAL: SMgrRelation hashtable corrupted |