Re: Bad planner performance for tables with empty tuples when using JIT - Mailing list pgsql-general

From Michael Lewis
Subject Re: Bad planner performance for tables with empty tuples when using JIT
Date
Msg-id CAHOFxGo5xJt02RmwAWrtv2K0jcqqxG-cDiR8FQbvb0WxdKhcgw@mail.gmail.com
Whole thread Raw
In response to Bad planner performance for tables with empty tuples when using JIT  (Jurrie Overgoor <postgresql-mailinglist@jurr.org>)
List pgsql-general
On Tue, Oct 27, 2020 at 6:14 AM Jurrie Overgoor <postgresql-mailinglist@jurr.org> wrote:
- I could turn off JIT in the server config, but I'd like to use the JIT   
feature where it's appropriate! 

I would do this, until PG14 and you can verify it works in most cases for you. 9.6 to 13 is already a big jump and you are already benefiting from many other changes. No need to opt-in to one that you know causes pain (some of the time). Else, try increasing jit_above_cost significantly.

[2] 
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=3d351d916b20534f973eda760cde17d96545d4c4

Given this is a feature (and also touches quite a few files), it would not be backpatched afaik.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: GSSAPI Authentication for pgadmin4 macOS client
Next
From: Adrian Klaver
Date:
Subject: Re: postgis update wants to install postgresql-13