From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Ondřej Bouda <obouda@email.cz>
Cc: Ondřej Bouda <bouda@edookit.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: backend crash on DELETE, reproducible locally
Date: Tue, 6 Nov 2018 16:45:53 -0300
Message-ID: <20181106194553.dynhd2xuivo56ymd@alvherre.pgsql> (raw)
In-Reply-To: <8e260d7c-13e8-b398-14dd-2e079ff7e833@email.cz>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: alvherre@2ndquadrant.com, obouda@email.cz, bouda@edookit.com, tgl@sss.pgh.pa.us, pgsql-general@lists.postgresql.org
Subject: Re: backend crash on DELETE, reproducible locally
In-Reply-To: <20181106194553.dynhd2xuivo56ymd@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox