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 09:53:08
Message-ID: 87tvhrhkz7.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> I found this article:

pabloa98> https://manual.limesurvey.org/Instructions_for_increasing_the_maximum_number_of_columns_in_PostgreSQL_on_Linux

Those instructions contain obvious errors.

pabloa98> It seems I should modify: uint8 t_hoff;
pabloa98> and replace it with something like: uint32 t_hoff; or uint64 t_hoff;

At the very least, that ought to be uint16 t_hoff; since there is never
any possibility of hoff being larger than 32k since that's the largest
allowed pagesize. However, if you modify that, it's then up to you to
ensure that all the code that assumes it's a uint8 is found and fixed.
I have no idea what else would break.

--
Andrew (irc:RhodiumToad)

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Sathish Kumar 2019-01-29 10:08:22 Anonymize Data
Previous Message Andrew Gierth 2019-01-29 09:09:56 Re: postgresql v11.1 Segmentation fault: signal 11: by running SELECT... JIT Issue?