Date: Tue, 6 Nov 2018 16:45:53 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: =?utf-8?Q?Ond=C5=99ej?= Bouda <obouda@email.cz>
Cc: =?utf-8?Q?Ond=C5=99ej?= Bouda <bouda@edookit.com>,
	Tom Lane <tgl@sss.pgh.pa.us>, pgsql-general@lists.postgresql.org
Subject: Re: backend crash on DELETE, reproducible locally
Message-ID: <20181106194553.dynhd2xuivo56ymd@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <8e260d7c-13e8-b398-14dd-2e079ff7e833@email.cz>
User-Agent: NeoMutt/20180716
Precedence: bulk

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