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 1igt3X-0002s4-Cb for pgsql-bugs@arkaria.postgresql.org; Mon, 16 Dec 2019 16:17:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1igt3V-0004QT-5P for pgsql-bugs@arkaria.postgresql.org; Mon, 16 Dec 2019 16:17:09 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1igt3U-0004MZ-Pq for pgsql-bugs@lists.postgresql.org; Mon, 16 Dec 2019 16:17:08 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1igt3S-0003DH-GF for pgsql-bugs@lists.postgresql.org; Mon, 16 Dec 2019 16:17:07 +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 xBGGGsNd012054; Mon, 16 Dec 2019 11:16:54 -0500 From: Tom Lane To: avinash varma cc: Heikki Linnakangas , pgsql-bugs@lists.postgresql.org Subject: Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11 In-reply-to: References: <24176.1576509007@sss.pgh.pa.us> Comments: In-reply-to avinash varma message dated "Mon, 16 Dec 2019 20:57:20 +0530" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <12052.1576513014.1@sss.pgh.pa.us> Date: Mon, 16 Dec 2019 11:16:54 -0500 Message-ID: <12053.1576513014@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk avinash varma writes: > Actually , we used the same backup to restore on both V10 & V11 , So the > data on both the versions is same. > After restore, we ran vacuum full analyze on both the servers . > default_statistics_target value "1000" is same on both the versions. > Used the same postgresql.conf , i,e it is same on both V10 and V11 You didn't answer the question: >> First thing to do is to look into pg_stats and see how large those >> arrays actually are in each case ... Also, please don't top-post when replying. It makes it hard for people to follow the conversation. regards, tom lane