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

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: pabloa98 <pabloa98(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: postgresql v11.1 Segmentation fault: signal 11: by running SELECT... JIT Issue?
Date: 2019-01-29 07:58:09
Message-ID: 8736pbj449.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>>>>> "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)

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message pabloa98 2019-01-29 08:11:13 Re: postgresql v11.1 Segmentation fault: signal 11: by running SELECT... JIT Issue?
Previous Message Tom Lane 2019-01-29 03:28:29 Re: postgresql v11.1 Segmentation fault: signal 11: by running SELECT... JIT Issue?