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 1i7n40-000488-0G for pgsql-hackers@arkaria.postgresql.org; Tue, 10 Sep 2019 20:48:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1i7n3y-0007rC-1V for pgsql-hackers@arkaria.postgresql.org; Tue, 10 Sep 2019 20:48:34 +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 1i7n3w-0007BZ-PF for pgsql-hackers@lists.postgresql.org; Tue, 10 Sep 2019 20:48:33 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1i7n3p-0000zl-Bf for pgsql-hackers@postgresql.org; Tue, 10 Sep 2019 20:48:31 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 70EFC217DD; Tue, 10 Sep 2019 16:48:24 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Tue, 10 Sep 2019 16:48:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=3zUVd9VhJHDkpTPw484byd0iwaWnGBvpelJngL8ys6s=; b=reJBcJuy HOP4B0eMHQXTcoJnW0esbZwXTXusg/BIJRLC93bQoaloOHmQvVbNHowMQi5SpPYy mdT28h7q8VNMqC6/FZ0ua3UPw7wtOgBaGhC3i/qp3PCBt7hOx9HlrtippdyrUTzD Pk4sKjyx0qm75N1EtDPFQhvLVOGhYbBEkoUfDv4cQ5mEv/WmOoMihiE1UH/Yq7AL /6lkAthG0fNEYllTD70zJ5/ZnEVWGttcWrQ719nrNfEWo7P1zhMa4c0v6Z7g31i1 Qeck042fJKK0+r31xCoS1djzMRzD04QOuoaI+Wuw1xXT+fZJs2uW0LtJp+CGg3Sn rGbjZuNc1w3HEw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrtddtgddufeduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfggtggugfgjfgesthekredttderudenucfhrhhomheptehlvhgr rhhoucfjvghrrhgvrhgruchfrhhomhcuvdhnugfsuhgrughrrghnthcuoegrlhhvhhgvrh hrvgesrghlvhhhrdhnohdqihhprdhorhhgqeenucffohhmrghinhepvdhnughquhgrughr rghnthdrtghomhenucfkphepudeltddrvddujedrudekfedrvddtvdenucfrrghrrghmpe hmrghilhhfrhhomheprghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrghenucev lhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from nimloth.alvh.no-ip.org (unknown [190.217.183.202]) by mail.messagingengine.com (Postfix) with ESMTPA id E4964D6005D; Tue, 10 Sep 2019 16:48:23 -0400 (EDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 10AEC123800; Tue, 10 Sep 2019 17:48:22 -0300 (-03) Date: Tue, 10 Sep 2019 17:48:22 -0300 From: Alvaro Herrera from 2ndQuadrant To: Richard Guo Cc: Etsuro Fujita , Amit Langote , PostgreSQL-development Subject: Re: A problem about partitionwise join Message-ID: <20190910204822.GA9494@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk So in this patch, the input restrictlist is modified to include the clauses generated by generate_join_implied_equalities_for_all. That doesn't seem okay -- doesn't it affect downstream usage of the restrictlist in the caller of set_joinrel_size_estimates? I wonder if it's possible to do this by using the ECs directly in have_partkey_equi_join instead of using them to create fake join clauses. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services