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 <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1iUxWO-0000yG-M5
	for pgsql-bugs@arkaria.postgresql.org; Wed, 13 Nov 2019 18:37:40 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1iUxWL-00011l-W9
	for pgsql-bugs@arkaria.postgresql.org; Wed, 13 Nov 2019 18:37:37 +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 <chhatani.mukesh@gmail.com>)
	id 1iUxWL-00011c-HQ
	for pgsql-bugs@lists.postgresql.org; Wed, 13 Nov 2019 18:37:37 +0000
Received: from n3.nabble.com ([162.255.23.22])
	by makus.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <chhatani.mukesh@gmail.com>)
	id 1iUxWE-00022p-NZ
	for pgsql-bugs@postgresql.org; Wed, 13 Nov 2019 18:37:36 +0000
Received: from n3.nabble.com (localhost [127.0.0.1])
	by n3.nabble.com (Postfix) with ESMTP id 7956118AA8E0B
	for <pgsql-bugs@postgresql.org>; Wed, 13 Nov 2019 11:37:30 -0700 (MST)
Date: Wed, 13 Nov 2019 11:37:30 -0700 (MST)
From: Mukesh Chhatani <chhatani.mukesh@gmail.com>
To: pgsql-bugs@postgresql.org
Message-ID: <1573670250461-0.post@n3.nabble.com>
In-Reply-To: <16109-26a1a88651e90608@postgresql.org>
References: <16109-26a1a88651e90608@postgresql.org>
Subject: Re: BUG #16109: Postgres planning time is high across version -
 10.6 vs 10.10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Precedence: bulk

All,

Update I was able to resolve the problem by changing - partitioned tables to
single table and changing data type of 2 columns used in the joins from
varchar to varchar(50).

FYI.. default_statistics_target was set to 10000 but I changed it 100 and
even to 1000 and still planning time was high.

Still working on the dataset so that more people can investigate the issues.



--
Sent from: https://www.postgresql-archive.org/PostgreSQL-bugs-f2117394.html