From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Ondřej Bouda <obouda@email.cz>
Cc: Ondřej Bouda <bouda@edookit.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: backend crash on DELETE, reproducible locally
Date: Tue, 06 Nov 2018 15:14:08 -0500
Message-ID: <333.1541535248@sss.pgh.pa.us> (raw)
In-Reply-To: <20181106194553.dynhd2xuivo56ymd@alvherre.pgsql>
References: <20181106194553.dynhd2xuivo56ymd@alvherre.pgsql>
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> What indexes are there in this table? Indexes on expressions are
> particularly suspect.
I had not looked at the "projection index" code before, and now that
I have, I am desperately unhappy with it. It's seriously buggy,
badly underdocumented, unbelievably inefficient, and it looks like
it creates a whole new set of reasons for unwanted recursion inside
the relcache. The relcache has got NO business calling cost_qual_eval,
for example.
Having said that, I'm not real sure how it ends up with this crash.
It looks like ProjIndexIsUnchanged is getting the wrong value for
the index column's typbyval, but how could that be?
regards, tom lane
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: tgl@sss.pgh.pa.us, alvherre@2ndquadrant.com, obouda@email.cz, bouda@edookit.com, pgsql-general@lists.postgresql.org
Subject: Re: backend crash on DELETE, reproducible locally
In-Reply-To: <333.1541535248@sss.pgh.pa.us>
* 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