Re: backend crash on DELETE, reproducible locally
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Ondřej Bouda <obouda@email.cz>, Ondřej Bouda <bouda@edookit.com>, pgsql-general@lists.postgresql.org
Date: 2018-11-06T20:14:08Z
Lists: pgsql-hackers, 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
Commits
-
Disable recheck_on_update optimization to avoid crashes.
- 05f84605dbeb 11.1 landed
- 5d28c9bd73e2 12.0 landed
-
Allow HOT updates for some expression indexes
- c203d6cf81b4 11.0 cited