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

From: pabloa98 <pabloa98(at)gmail(dot)com>
To: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
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 10:19:36
Message-ID: CAEjudX7Ycy=mCiPAHvtGe6YJXggiJG1dGMtq7AW1zCU6ZwBLOQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)tao11(dot)riddles(dot)org(dot)uk>
wrote:

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

Browse pgsql-general by date

  From Date Subject
Next Message Sathish Kumar 2019-01-29 12:24:19 Table Replication
Previous Message Sathish Kumar 2019-01-29 10:08:22 Anonymize Data