Re: postgresql v11.1 Segmentation fault: signal 11: by running SELECT... JIT Issue?

I did not modify it.

I guess I should make it bigger than 1765. is 2400 or 3200 fine?

My apologies if my questions look silly. I do not know about the internal
format of the database.

Pablo

On Mon, Jan 28, 2019 at 11:58 PM Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
wrote:

> >>>>> "pabloa98" == pabloa98 <pabloa98(at)gmail(dot)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)
>