Re: backend crash on DELETE, reproducible locally

On 11/03/2018 02:19 PM, obouda@email.cz wrote:
> Hello,
>
> we reached the exactly same problem after upgrading to PostgreSQL 11 - the 
> server crashed on a DELETE statement with a trigger.We also observed an 
> AFTER DELETE trigger receiving NULL values in OLD. Now I see the problem 
> seems to be solved (theoretically). Unfortunately, we are not able to 
> build the server with the patch, so we cannot confirm that. However, when 
> we just copied the database (within the same server), the same DELETE 
> executed on the copy with no problems.
>
> I would like to ask, however: could the same problemarise from an UPDATE 
> statement (also on a table with an AFTER trigger), or would that be 
> another bug (technical details below)?
> As the bug causes our production servers segfault several times a day, 
> we'd like to solve the problem as soon as possible. Do I understand it 
> correctly that if we dump and restore the database, the bug should not 
> occur (until the next ALTER TABLE ADD COLUMN - which we'll avoid until the 
> patch is released)?

You can dump that single table, truncate the table (presuming no FKs) and 
then restore it.

-- 
Angular momentum makes the world go 'round.