| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PG v12.2 - Setting jit_above_cost is causing the server to crash |
| Date: | 2020-02-24 07:16:49 |
| Message-ID: | 20200224071649.ggrhej4n7dq4ruwo@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
Hi,
On 2020-02-24 12:16:08 +0530, Aditya Toshniwal wrote:
> The PG 12.2 server is crashing on setting the jit_above_cost param. Below
> is the output.
> postgres=# SELECT count(*) FROM pg_class;
>
> server closed the connection unexpectedly
>
> This probably means the server terminated abnormally
>
> before or while processing the request.
>
> The connection to the server was lost. Attempting reset: Failed.
This isn't reproducible here. Are you sure that you're running on a
clean installation?
If not, we'd at least need a backtrace to figure out what's going on.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aditya Toshniwal | 2020-02-24 07:35:19 | Re: PG v12.2 - Setting jit_above_cost is causing the server to crash |
| Previous Message | Aditya Toshniwal | 2020-02-24 06:59:06 | Re: PG v12.2 - Setting jit_above_cost is causing the server to crash |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2020-02-24 07:28:57 | Re: ALTER TABLE ... SET STORAGE does not propagate to indexes |
| Previous Message | Aditya Toshniwal | 2020-02-24 06:59:06 | Re: PG v12.2 - Setting jit_above_cost is causing the server to crash |