On 2018-Nov-06, Ondřej Bouda wrote: > So we dumped and restored all our databases. After that, the crash on DELETE > never occurred (before, it was several times a day). However, the crash on > UPDATE still occurs on specific rows. We are quite certain no ALTER TABLE > statement was executed on the table after the restore. > There are two AFTER INSERT OR UPDATE constraint triggers and one BEFORE > INSERT OR UPDATE trigger on the table, all of which are implemented in > plpgsql. Multiple physical servers, on separate databases with identical > schema, crash on the same type of UPDATE query (different just in concrete > values to be updated). The same code worked perfectly on 10.x. > > See the attached backtrace below. Can we do something else to catch the bug? > Or can we hope for this bug to be already fixed and released in the upcoming > version?
Hmm, this one smells like c203d6cf81b4 -- haven't seen any fixes for that one. Can you share more details on this? I think the failing update is on table with oid=557732818, but I might be wrong. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
