From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mladen Gogala <gogala.mladen@gmail.com>
cc: pgsql-general@lists.postgresql.org
Subject: Re: Interesting fail when migrating Pg from Ubuntu Bionic to Focal
In-reply-to: <780e8797-b5a8-f02f-fbea-e01b625a34a7@gmail.com>
References: <20220303150428.GA26036@depesz.com>
 <20220303151156.GB26036@depesz.com> <20220303163921.GA10776@depesz.com>
 <20220303164401.GA13056@depesz.com> <3969790.1646420992@sss.pgh.pa.us>
 <20220304204510.GA21340@depesz.com> <3984384.1646431394@sss.pgh.pa.us>
 <780e8797-b5a8-f02f-fbea-e01b625a34a7@gmail.com>
Comments: In-reply-to Mladen Gogala <gogala.mladen@gmail.com>
	message dated "Fri, 04 Mar 2022 21:42:53 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4008272.1646448513.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 04 Mar 2022 21:48:33 -0500
Message-ID: <4008273.1646448513@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/4008273.1646448513%40sss.pgh.pa.us>
Precedence: bulk

Mladen Gogala <gogala.mladen@gmail.com> writes:
> On 3/4/22 17:03, Tom Lane wrote:
>> Mmm ... it might have just been that the planner chose not to use
>> JIT when it thought there were fewer rows involved.  Did you check
>> with EXPLAIN that these cut-down cases still used JIT?

> This is interesting and informative answer. How do I check whether JIT =

> is used in the explain plan? Can you give me an example?

If EXPLAIN prints some stuff about JIT, then JIT is going to be
used, otherwise not.  Here's an example from my (entirely
unsuccessful) attempts to duplicate depesz's problem:

=3D# explain select p.proname, (SELECT rolname from pg_catalog.pg_roles wh=
ere oid =3D p.proowner) from pg_proc p;
                                          QUERY PLAN                      =
                    =

--------------------------------------------------------------------------=
--------------------
 Seq Scan on pg_proc p  (cost=3D0.00..393587.22 rows=3D47243 width=3D128)
   SubPlan 1
     ->  Index Scan using pg_authid_oid_index on pg_authid  (cost=3D0.28..=
8.30 rows=3D1 width=3D64)
           Index Cond: (oid =3D p.proowner)
 JIT:
   Functions: 8
   Options: Inlining false, Optimization false, Expressions true, Deformin=
g true
(7 rows)

			regards, tom lane