Re: postgresql v11.1 Segmentation fault: signal 11: by running SELECT... JIT Issue? - Mailing list pgsql-general

From Andrew Gierth
Subject Re: postgresql v11.1 Segmentation fault: signal 11: by running SELECT... JIT Issue?
Date
Msg-id 8736pbj449.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to postgresql v11.1 Segmentation fault: signal 11: by running SELECT...JIT Issue?  (pabloa98 <pabloa98@gmail.com>)
Responses Re: postgresql v11.1 Segmentation fault: signal 11: by runningSELECT... JIT Issue?  (pabloa98 <pabloa98@gmail.com>)
List pgsql-general
>>>>> "pabloa98" == pabloa98  <pabloa98@gmail.com> writes:

 pabloa98> the table baseline_denull has 1765 columns,

Uhh...

#define MaxHeapAttributeNumber    1600    /* 8 * 200 */

Did you modify that?

(The back of my envelope says that on 64bit, the largest usable t_hoff
would be 248, of which 23 is fixed overhead leaving 225 as the max null
bitmap size, giving a hard limit of 1800 for MaxTupleAttributeNumber and
1799 for MaxHeapAttributeNumber. And the concerns expressed in the
comments above those #defines would obviously apply.)

-- 
Andrew (irc:RhodiumToad)


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: postgresql v11.1 Segmentation fault: signal 11: by running SELECT... JIT Issue?
Next
From: pabloa98
Date:
Subject: Re: postgresql v11.1 Segmentation fault: signal 11: by runningSELECT... JIT Issue?