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-performance-owner+archive@lists.postgresql.org>)
	id 1gdDYg-0007NA-N9
	for pgsql-performance@arkaria.postgresql.org; Sat, 29 Dec 2018 12:17:38 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1gdDYf-0002Qp-8M
	for pgsql-performance@arkaria.postgresql.org; Sat, 29 Dec 2018 12:17: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 <jfinnert@amazon.com>)
	id 1gdDYe-0002IK-SA
	for pgsql-performance@lists.postgresql.org; Sat, 29 Dec 2018 12:17:37 +0000
Received: from n3.nabble.com ([162.255.23.22])
	by makus.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <jfinnert@amazon.com>)
	id 1gdDYc-0007ns-AX
	for pgsql-performance@postgresql.org; Sat, 29 Dec 2018 12:17:35 +0000
Received: from n3.nabble.com (localhost [127.0.0.1])
	by n3.nabble.com (Postfix) with ESMTP id 34E941118DDDA
	for <pgsql-performance@postgresql.org>; Sat, 29 Dec 2018 05:17:33 -0700 (MST)
Date: Sat, 29 Dec 2018 05:17:33 -0700 (MST)
From: Jim Finnerty <jfinnert@amazon.com>
To: pgsql-performance@postgresql.org
Message-ID: <1546085853213-0.post@n3.nabble.com>
In-Reply-To: 
 <CAMkU=1w2MDqZOvwqeB56vPdc1b0JOsBwPx3xcA8MvF4vzQLdZQ@mail.gmail.com>
References: <1543227078813-0.post@n3.nabble.com>
 <CAMkU=1w2MDqZOvwqeB56vPdc1b0JOsBwPx3xcA8MvF4vzQLdZQ@mail.gmail.com>
Subject: Re: Optimizer choosing the wrong plan
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
List-Id: <pgsql-performance.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-performance@lists.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-performance>
Precedence: bulk

re: It would interesting if you can upgrade a copy of your server to v11 and
try it there.  We made changes to ANALYZE in that version which were
intended to improve this situation, and it would be nice to know if it
actually did so for your case.  

Jeff, can you describe the changes that were made to ANALYZE in v11, please?

I've found that running ANALYZE on v10 on the Join Order Benchmark, using
the default statistics target of 100, produces quite unstable results, so
I'd be interested to hear what has been improved in v11.

    /Jim



-----
Jim Finnerty, AWS, Amazon Aurora PostgreSQL
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-performance-f2050081.html