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

From pabloa98
Subject Re: postgresql v11.1 Segmentation fault: signal 11: by runningSELECT... JIT Issue?
Date
Msg-id CAEjudX7Ycy=mCiPAHvtGe6YJXggiJG1dGMtq7AW1zCU6ZwBLOQ@mail.gmail.com
Whole thread Raw
In response to Re: postgresql v11.1 Segmentation fault: signal 11: by running SELECT... JIT Issue?  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
List pgsql-general
I appreciate your advice. I will check the number of columns in that table. 



On Tue, Jan 29, 2019, 1:53 AM Andrew Gierth <andrew@tao11.riddles.org.uk> wrote:
>>>>> "pabloa98" == pabloa98  <pabloa98@gmail.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)

pgsql-general by date:

Previous
From: Sathish Kumar
Date:
Subject: Anonymize Data
Next
From: Sathish Kumar
Date:
Subject: Table Replication