Re: backend crash on DELETE, reproducible locally

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Ondřej Bouda <obouda(at)email(dot)cz>
Cc: Ondřej Bouda <bouda(at)edookit(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: backend crash on DELETE, reproducible locally
Date: 2018-11-06 19:45:53
Message-ID: 20181106194553.dynhd2xuivo56ymd@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On 2018-Nov-06, Ondřej Bouda wrote:

> > 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.
>
> That's exactly the table, public.schedulecard.
> We issue an UPDATE changing some of its columns. E.g.,
>
> UPDATE public.schedulecard SET ext_ident=null,
> rotates=false,period_num=1,period_day=2 WHERE id=3817

What indexes are there in this table? Indexes on expressions are
particularly suspect.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Condor 2018-11-06 19:49:17 Re: Question about index on different tablespace and rebuild it
Previous Message Ondřej Bouda 2018-11-06 19:37:58 Re: backend crash on DELETE, reproducible locally

Browse pgsql-hackers by date

  From Date Subject
Next Message Isaac Morland 2018-11-06 19:46:28 Re: Disallow setting client_min_messages > ERROR?
Previous Message Ondřej Bouda 2018-11-06 19:37:58 Re: backend crash on DELETE, reproducible locally