Date: Thu, 20 Sep 2018 10:30:09 -0700
From: Andres Freund <andres@anarazel.de>
To: Christoph Berg <myon@debian.org>,
	PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: [patch] Support LLVM 7
Message-ID: <20180920173009.ywi5grbotl7um65p@alap3.anarazel.de>
References: <20180912124517.GD24584@msg.df7cb.de>
 <20180912210338.h3vsss5lkuu26ua2@alap3.anarazel.de>
 <20180912210734.GB5666@msg.df7cb.de>
 <20180916074833.GB4707@msg.df7cb.de>
 <20180919222600.myk5nec6unhrj45k@alap3.anarazel.de>
 <20180920081044.GA16897@msg.df7cb.de>
 <20180920131814.GC16897@msg.df7cb.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180920131814.GC16897@msg.df7cb.de>
Precedence: bulk

On 2018-09-20 15:18:14 +0200, Christoph Berg wrote:
> Re: To Andres Freund 2018-09-20 <20180920081044.GA16897@msg.df7cb.de>
> > > > 2018-09-15 10:49:25.052 UTC [26458] DETAIL:  Failed process was running: SELECT '' AS tf_12, BOOLTBL1.*, BOOLTBL2.*
> > > > 	   FROM BOOLTBL1, BOOLTBL2
> > > > 	   WHERE BOOLTBL2.f1 <> BOOLTBL1.f1;
> > > > 2018-09-15 10:49:25.052 UTC [26458] LOG:  terminating any other active server processes
> > > 
> > > Hm. Is there any chance to get a backtrace for this one?  This could,
> > > although I think less likely so, also be a postgres issue
> > > (e.g. generating code for the wrong microarch).
> > 
> > I'll see if I can find a porterbox to get a backtrace.

Hm, this is pretty helpful.  Sorry to ask, but could you a) turn on
jit_debugging_support (connection start) b) jit_dump_bitcode.

Then reproduce again.  After that, it'd be helpful to get:
1) /proc/cpuinfo
2) the "newest" *.bc file from the data directory
3) a backtrace
4) gdb disassemble at the point of the error.

Greetings,

Andres Freund