Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l0uzf-0005bT-DK for pgsql-bugs@arkaria.postgresql.org; Sat, 16 Jan 2021 23:28:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l0uzd-0005j0-W1 for pgsql-bugs@arkaria.postgresql.org; Sat, 16 Jan 2021 23:28:29 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l0uzd-0005it-QB for pgsql-bugs@lists.postgresql.org; Sat, 16 Jan 2021 23:28:29 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l0uzb-0000af-4K for pgsql-bugs@postgresql.org; Sat, 16 Jan 2021 23:28:29 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 10GNSNEC106471; Sat, 16 Jan 2021 18:28:23 -0500 From: Tom Lane To: Kisung Kim cc: pgsql-bugs@postgresql.org Subject: Re: BUG #16824: Planner chooses poor path on query with Merge Join and pagination In-reply-to: <1610836457734-0.post@n3.nabble.com> References: <16824-cac06100763db5ae@postgresql.org> <1343668.1610583399@sss.pgh.pa.us> <1610836457734-0.post@n3.nabble.com> Comments: In-reply-to Kisung Kim message dated "Sat, 16 Jan 2021 15:34:17 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <106469.1610839703.1@sss.pgh.pa.us> Date: Sat, 16 Jan 2021 18:28:23 -0500 Message-ID: <106470.1610839703@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Kisung Kim writes: > Tom Lane-2 wrote >> This is an empirical decision based on the >> frequency with which such a deduction would help versus the planner >> cycles that would be spent looking for such cases. > Is there any thing referring to this decision, like mail threads or > conference materials? [ shrug... ] It's doubtless been discussed on pgsql-hackers in the past, but I don't plan to go digging through those archives for you. Looking for constraint exclusion via https://www.postgresql.org/search/?m=1 or your favorite search engine might help you. regards, tom lane