On Mon, Oct 16, 2023 at 11:46 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Richard Guo <guofenglinux@gmail.com> writes: > And 'git bisect' says that the first bad commit is 2489d76c, which makes > me confused because the problemed query does not seem to involve > nullingrels stuff.
Probably the reason is that addition of nullingrels fields to the Vars pushed it over the edge of needing to be out-of-line. The test case is very close to the line as stated --- for example, I found that it didn't crash if I changed "en_AG.utf8" to "C", and wasted some time pursuing the idea that the collation had something to do with it. The crash got much more stable after adding a couple more dummy clauses to the CHECK condition, and I've also reproduced it with clauses as straightforward as "c0 < 'very-long-constant'".
Ah, this clears up my confusion. Thanks for the fix.
