Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cYz5A-0002D0-OG for pgsql-performance@arkaria.postgresql.org; Wed, 01 Feb 2017 17:52:36 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cYz5A-0002hr-7t for pgsql-performance@arkaria.postgresql.org; Wed, 01 Feb 2017 17:52:36 +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_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cYz58-0002fX-SD for pgsql-performance@postgresql.org; Wed, 01 Feb 2017 17:52:34 +0000 Received: from smtp26.services.sfr.fr ([93.17.128.10]) by magus.postgresql.org with esmtps (TLS1.0:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cYz56-0000FY-Js for pgsql-performance@postgresql.org; Wed, 01 Feb 2017 17:52:34 +0000 Received: from debian.fr (130.215.20.109.rev.sfr.net [109.20.215.130]) by msfrf2622.sfr.fr (SMTP Server) with ESMTP id 121581C15DC19; Wed, 1 Feb 2017 18:52:30 +0100 (CET) Received: from debian.fr (130.215.20.109.rev.sfr.net [109.20.215.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by msfrf2622.sfr.fr (SMTP Server) with ESMTPS; Wed, 1 Feb 2017 18:52:28 +0100 (CET) Received: by debian.fr (Postfix, from userid 1000) id 464664803A1; Mon, 30 Jan 2017 09:24:11 +0100 (CET) From: Philippe Ivaldi To: "pgsql-performance@postgresql.org" Cc: Albe Laurenz Subject: Re: Chaotic query planning ? In-Reply-To: (Albe Laurenz's message of "Thu, 19 Jan 2017 16:05:15 +0000") Organization: OVYA References: <87ziinru9c.fsf@piprime.fr> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) Date: Mon, 30 Jan 2017 09:24:11 +0100 Message-ID: <87r33l6jmc.fsf@piprime.fr> MIME-Version: 1.0 X-sfr-mailing: LEGIT Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org Albe Laurenz wrote > […] > Experiment with raising join_collapse_limit and from_collapse_limit to 11. Thank you, this solve the problem. > Alternatively, optimize the join order by hand and don't tune the parameters. What is surprising is that there is no apparent/logical optimal strategy. Best regards, -- PI -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance