From: | Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
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:35:19 |
Message-ID: | CAM9w-_n62_TD54hjPRMo-V=4FDj_vHb4mGabDVENnMzRabC9ww@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
Hi Andres,
On Mon, Feb 24, 2020 at 12:46 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
>
> 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?
>
Yes I did a fresh installation using installer provided here -
https://www.enterprisedb.com/downloads/postgresql
>
> If not, we'd at least need a backtrace to figure out what's going on.
>
Please let me know how can I provide required info.
>
> Greetings,
>
> Andres Freund
>
--
Thanks and Regards,
Aditya Toshniwal
pgAdmin Hacker | Sr. Software Engineer | EnterpriseDB India | Pune
"Don't Complain about Heat, Plant a TREE"
From | Date | Subject | |
---|---|---|---|
Next Message | Imre Samu | 2020-02-24 07:44:33 | Re: PG v12.2 - Setting jit_above_cost is causing the server to crash |
Previous Message | Andres Freund | 2020-02-24 07:16:49 | Re: PG v12.2 - Setting jit_above_cost is causing the server to crash |
From | Date | Subject | |
---|---|---|---|
Next Message | Imre Samu | 2020-02-24 07:44:33 | Re: PG v12.2 - Setting jit_above_cost is causing the server to crash |
Previous Message | Peter Eisentraut | 2020-02-24 07:28:57 | Re: ALTER TABLE ... SET STORAGE does not propagate to indexes |