Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nQKNu-00071G-TF for pgsql-general@arkaria.postgresql.org; Sat, 05 Mar 2022 02:43:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nQKNt-0007ZM-Pl for pgsql-general@arkaria.postgresql.org; Sat, 05 Mar 2022 02:43:05 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nQKNt-0007ZD-CW for pgsql-general@lists.postgresql.org; Sat, 05 Mar 2022 02:43:05 +0000 Received: from mail-qv1-xf29.google.com ([2607:f8b0:4864:20::f29]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nQKNm-00073u-Io for pgsql-general@lists.postgresql.org; Sat, 05 Mar 2022 02:43:05 +0000 Received: by mail-qv1-xf29.google.com with SMTP id im7so1462412qvb.4 for ; Fri, 04 Mar 2022 18:42:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to; bh=ZHFw33Mg4XprSSqNubjCPvAXSf9miVaXSdXzoNhAP94=; b=lD+RUnHvYqafllmJw9RYwri5R/4+WQX0i8Fpo0WDgCoQ6rPPlTrar2ChEraar2mE8m C2m9jbfzijEKZOBZ3F6H/Wvv6tlnWCsF0A/z4p5s+Iyy2UydX1+QAtfcGD5rvZVgU1nl BMvyyDfpAcNSKTl3fZJ+ZIn4kd/KTqVIyPqAZY6h2/4amz0GlghgWIQcj3Z4gCNBClyX aDjFDpVZo5+7clK4PDtWIm+wUymWKTJEH8PN8eLzMmDUgAWVsVnrZExE2H5NBcpkU+fD WdNb81YMP/Ph48BIxJ62zssxUl4viFic37l5omJA5+55PXZWwPb6q6SZaPtjjwCcN903 rs/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to; bh=ZHFw33Mg4XprSSqNubjCPvAXSf9miVaXSdXzoNhAP94=; b=VscdYxZbrCJ7O3ELjyTl3xzX7NkxS0DT02AmWzSlz4QFGXkKKAmqsg4psnEoxqGt5k g1vF/bcqebwDPyL9I91EYalfz8An4O3aouywNyt4gONHlHmba5FadM7K/8QUMCVx/mx7 SCQ5mwLa4Yt7lf4a2T5Pd+aPNIsE9aqSRef2x4lFrP8yAN4ztm5ZvY+L6ORUmCWOBJnC OgCtFGboQ4fLoI4f7tFrSYFS6CnxANdjp+0ETiSE/raI295e0vkgWZqrImutFskIC6DA /mn1n24Wc3Bs/dHctYIaaiN2SzuIQD/QawLy9ombgaOgEU22jAFNug2Epz8TnXog4Vc0 V+HA== X-Gm-Message-State: AOAM533nQQLORTsMvHaeFCFptOOQaxZDyeo2DETtWs7xnIGo0OR8aS2T dLhHDw3qSJP6g/A76POFclKTSlmYp7Q= X-Google-Smtp-Source: ABdhPJyQZhJ6dALmgJxFSvJ01Fa5WLyt+aUoOrt5+mE7INoV9Qsp8yYkCVuCU1u/1kXKNAi7+JMhrQ== X-Received: by 2002:a05:6214:2309:b0:435:374d:4bbb with SMTP id gc9-20020a056214230900b00435374d4bbbmr1079609qvb.105.1646448175841; Fri, 04 Mar 2022 18:42:55 -0800 (PST) Received: from [192.168.2.100] (pool-72-79-19-93.nwrknj.east.verizon.net. [72.79.19.93]) by smtp.gmail.com with ESMTPSA id f13-20020ac87f0d000000b002dce143f369sm4711213qtk.53.2022.03.04.18.42.54 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 04 Mar 2022 18:42:55 -0800 (PST) Content-Type: multipart/alternative; boundary="------------dz5W96baas2tcw0ObN7rHCbR" Message-ID: <780e8797-b5a8-f02f-fbea-e01b625a34a7@gmail.com> Date: Fri, 4 Mar 2022 21:42:53 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: Interesting fail when migrating Pg from Ubuntu Bionic to Focal Content-Language: en-US To: pgsql-general@lists.postgresql.org 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> From: Mladen Gogala In-Reply-To: <3984384.1646431394@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------dz5W96baas2tcw0ObN7rHCbR Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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? TIA -- Mladen Gogala Database Consultant Tel: (347) 321-1217 https://dbwhisperer.wordpress.com --------------dz5W96baas2tcw0ObN7rHCbR Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
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?

TIA

-- 
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
https://dbwhisperer.wordpress.com
--------------dz5W96baas2tcw0ObN7rHCbR--