Alvaro Herrera 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 h
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 restor
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 recen
Daulat Ram 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.postg
5-17 06:41:19.887 UTC [11] LOG: redo starts at 5E/170349E8
2019-05-17 06:41:19.954 UTC [11] FATAL: SMgrRelation hashtable corrupted
2019-05-17 06:41:19.954 UTC [11] CONTEXT: WAL redo at 5E/17061648 for
Transaction/COMMIT: 2019-05-17 06:39:46.902988+00; rels: base/59265/105367
base/59265/105349
