| From: | Marc <postgres(at)arcict(dot)com> |
|---|---|
| To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Postgres 12.1 : UPPER() in WHERE clause restarts server |
| Date: | 2020-02-27 17:08:08 |
| Message-ID: | 2494CEB2-A63A-4D6E-A442-EB5A670118C5@arcict.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hello Tom,
To whom do we report our findings regarding this issue ?
I can offer you a Belgian waffle to go with you caffeine.
Kindest Regards,
Marc
On 25 Feb 2020, at 10:35, Nick Renders wrote:
> Hi Tom,
>
> 1. we used the EDB installer.
>
> 2. turning JIT off did make the problem go away. So I guess this was
> causing the Postgres process to crash all along.
>
> Thanks for the help,
>
> Nick
>
>
> On 24 Feb 2020, at 16:24, Tom Lane wrote:
>
>> "Nick Renders" <postgres(at)arcict(dot)com> writes:
>>> We have set up a new test environment running PostgreSQL v12.2 on
>>> macOS
>>> 10.14 and the issue is still there.
>>
>> Some nearby threads prompt these two questions:
>>
>> 1. Are you using your own build, or is this from EDB's installer?
>>
>> 2. If the latter, does turning JIT off ("set jit = off") make the
>> problem go away?
>>
>> There is as yet no "native" support for --with-llvm on macOS,
>> ie Apple themselves don't provide sufficient support for that.
>> EDB seem to have hacked up something that sort of works, but
>> only sort of.
>>
>> regards, tom lane
ARC - your Apple service partner
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2020-02-27 18:12:51 | Re: Postgres 12.1 : UPPER() in WHERE clause restarts server |
| Previous Message | Ireneusz Pluta/wp.pl | 2020-02-27 16:33:47 | Re: Need to find the no. of connections for a database |