Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ihFlQ-0000hk-VS for pgsql-bugs@arkaria.postgresql.org; Tue, 17 Dec 2019 16:32:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ihFlP-0003Pw-Kb for pgsql-bugs@arkaria.postgresql.org; Tue, 17 Dec 2019 16:31:59 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ihFlP-0003Pp-Bp for pgsql-bugs@lists.postgresql.org; Tue, 17 Dec 2019 16:31:59 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ihFlN-0003dM-47 for pgsql-bugs@lists.postgresql.org; Tue, 17 Dec 2019 16:31:58 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id xBHGVYtw026234; Tue, 17 Dec 2019 11:31:34 -0500 From: Tom Lane To: Tomas Vondra cc: avinash varma , Pavel Stehule , Heikki Linnakangas , PostgreSQL mailing lists Subject: Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11 In-reply-to: <20191217120751.34fmwkshfanjqws2@development> References: <24176.1576509007@sss.pgh.pa.us> <12053.1576513014@sss.pgh.pa.us> <20191217120751.34fmwkshfanjqws2@development> Comments: In-reply-to Tomas Vondra message dated "Tue, 17 Dec 2019 13:07:51 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <26232.1576600294.1@sss.pgh.pa.us> Date: Tue, 17 Dec 2019 11:31:34 -0500 Message-ID: <26233.1576600294@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Tomas Vondra writes: > You've been asked (at least) twice to check size of statistics stored in > pg_stats. It's really hard to help you when you don't provide important > information like this. Apparently we need to be more explicit. What we want to see is select most_common_vals from pg_stats where tablename = 'child' and attname = 'id'; select most_common_vals from pg_stats where tablename = 'core' and attname = 'groupid'; from both databases. (Adjust as necessary if those weren't the real table and column names.) We probably don't need the specific array elements, but we do want to know how big those arrays are. regards, tom lane