On Sun, Oct 8, 2023 at 10:55 PM Suraj Kharage < suraj.khar...@enterprisedb.com> wrote:
> It looks like an issue with JIT. If I disable the JIT then the above query > runs successfully. > > postgres=# set jit to off; > > SET > > postgres=# SELECT * FROM rm32044_t1 LEFT JOIN rm32044_t2 ON > rm32044_t1.pkey = rm32044_t2.pkey, rm32044_t3 LEFT JOIN rm32044_t4 ON > rm32044_t3.pkey = rm32044_t4.pkey order by rm32044_t1.pkey,label,hidden; > > pkey | val | pkey | label | hidden | pkey | val | pkey > > ------+------+------+---------+--------+------+-----+------ > > 1 | row1 | 1 | hidden | t | 1 | 1 | > > 1 | row1 | 1 | hidden | t | 2 | 1 | > > 2 | row2 | 2 | visible | f | 1 | 1 | > > 2 | row2 | 2 | visible | f | 2 | 1 | > > (4 rows) > > Any idea on this? > No, but I found a few previous threads complaining about JIT not working on s390x. https://www.postgresql.org/message-id/4106722.1616177...@sss.pgh.pa.us https://www.postgresql.org/message-id/3ba50664-56a2-bcf4-2b24-05a3e0a75...@enterprisedb.com https://www.postgresql.org/message-id/20200715091509.GA3354074%40msg.df7cb.de The most interesting email I found in those threads was this one: http://postgr.es/m/3358505.1594912...@sss.pgh.pa.us The backtrace there is different from the one you posted here in significant ways, but it seems like both that case and this one involve a null pointer showing up for a non-null pass-by-reference datum. That doesn't seem like a whole lot to go on, but maybe somebody who understands the JIT stuff better than I do will have an idea. -- Robert Haas EDB: http://www.enterprisedb.com
