| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Daulat Ram <Daulat(dot)Ram(at)exponential(dot)com> |
| Cc: | "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 13:30:05 |
| Message-ID: | 6414.1558099805@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Daulat Ram <Daulat(dot)Ram(at)exponential(dot)com> writes:
> My Postgres 11.2 container is not started due to the below error message. It is in streaming replication environment.
> 2019-05-17 06:41:19.954 UTC [11] FATAL: SMgrRelation hashtable corrupted
Yes, this is probably the same issue reported in
https://www.postgresql.org/message-id/15672-b9fa7db32698269f@postgresql.org
https://www.postgresql.org/message-id/15684-4ef33de3271cf929@postgresql.org
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-05-17 15:34:16 | Re: FATAL: SMgrRelation hashtable corrupted |
| Previous Message | nigel.andersen | 2019-05-17 11:06:11 | Re: Upgrading 9.1.17 to which version? |