Re: backend crash on DELETE, reproducible locally - Mailing list pgsql-general

From Tom Lane
Subject Re: backend crash on DELETE, reproducible locally
Date
Msg-id 333.1541535248@sss.pgh.pa.us
Whole thread Raw
In response to Re: backend crash on DELETE, reproducible locally  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-general
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


pgsql-general by date:

Previous
From: Ondřej Bouda
Date:
Subject: Re: backend crash on DELETE, reproducible locally
Next
From: Tom Lane
Date:
Subject: Re: backend crash on DELETE, reproducible locally