From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
---|---|
To: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Bugs in TOAST handling, OID assignment and redo recovery |
Date: | 2018-04-10 12:34:39 |
Message-ID: | 1523363679.4685.10.camel@oopsware.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Am Dienstag, den 10.04.2018, 15:59 +0530 schrieb Pavan Deolasee:
> One of our 2ndQuadrant support customers recently reported a sudden
> rush of
> TOAST errors post a crash recovery, nearly causing an outage. Most
> errors
> read like this:
>
> ERROR: unexpected chunk number 0 (expected 1) for toast value nnnn
>
> While we could bring back the cluster to normal quickly using some
> workarounds, I investigated this in more detail and identified two
> long
> standing bugs in TOAST as well as redo recovery.
Wow! I'm currently also investigating issues on a customer system, too,
where suddenly TOAST errors arised after shutdown immediate.
I haven't dug into your findings yet, but it seems to perfectly fit
into the reports i got.
Thanks,
Bernd
From | Date | Subject | |
---|---|---|---|
Next Message | David Steele | 2018-04-10 12:55:52 | Re: [PATCH][PROPOSAL] Refuse setting toast.* reloptions when TOAST table does not exist |
Previous Message | Peter Eisentraut | 2018-04-10 12:28:29 | Re: [PATCH] pg_hba.conf : new auth option : clientcert=verify-full |