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

Поиск
Список
Период
Сортировка
От pabloa98
Тема Re: postgresql v11.1 Segmentation fault: signal 11: by runningSELECT... JIT Issue?
Дата
Msg-id CAEjudX7=Lvwh+viagYetGJKMQgKMGinrPQTshhgAQXCd=eeAog@mail.gmail.com
обсуждение исходный текст
Ответ на Re: postgresql v11.1 Segmentation fault: signal 11: by running SELECT... JIT Issue?  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
Ответы Re: postgresql v11.1 Segmentation fault: signal 11: by runningSELECT... JIT Issue?  (pabloa98 <pabloa98@gmail.com>)
Re: postgresql v11.1 Segmentation fault: signal 11: by running SELECT... JIT Issue?  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
Список pgsql-general
Дерево обсуждения
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@tao11.riddles.org.uk> wrote:
>>>>> "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 по дате отправления:

Предыдущее
От: Andrew Gierth
Дата:
Сообщение: Re: postgresql v11.1 Segmentation fault: signal 11: by running SELECT... JIT Issue?
Следующее
От: pabloa98
Дата:
Сообщение: Re: postgresql v11.1 Segmentation fault: signal 11: by runningSELECT... JIT Issue?