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 1hSsx0-0007mO-7J for pgsql-advocacy@arkaria.postgresql.org; Tue, 21 May 2019 00:48:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hSswy-0006uR-Ua for pgsql-advocacy@arkaria.postgresql.org; Tue, 21 May 2019 00:48:16 +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 1hSswy-0006tl-JH for pgsql-advocacy@lists.postgresql.org; Tue, 21 May 2019 00:48:16 +0000 Received: from tama50.ecl.ntt.co.jp ([129.60.39.147]) by makus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hSswv-0000i6-V4 for pgsql-advocacy@lists.postgresql.org; Tue, 21 May 2019 00:48:15 +0000 Received: from vc2.ecl.ntt.co.jp (vc2.ecl.ntt.co.jp [129.60.86.154]) by tama50.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id x4L0mAbs002411; Tue, 21 May 2019 09:48:10 +0900 Received: from vc2.ecl.ntt.co.jp (localhost [127.0.0.1]) by vc2.ecl.ntt.co.jp (Postfix) with ESMTP id BBDD763858D; Tue, 21 May 2019 09:48:10 +0900 (JST) Received: from jcms-pop21.ecl.ntt.co.jp (jcms-pop21.ecl.ntt.co.jp [129.60.87.134]) by vc2.ecl.ntt.co.jp (Postfix) with ESMTP id B01CE638580; Tue, 21 May 2019 09:48:10 +0900 (JST) Received: from [127.0.0.1] (unknown [129.60.241.61]) by jcms-pop21.ecl.ntt.co.jp (Postfix) with ESMTPSA id A71FC4007CA; Tue, 21 May 2019 09:48:10 +0900 (JST) Subject: Re: PostgreSQL 12: Feature Highlights References: <830415f7-78ec-ef7b-0f73-0e810ef87f91@postgresql.org> <20190516182628.kbkiajfnlooocgyg@momjian.us> <0cf10a27-c6a0-de4a-cd20-ab7493ea7422@lab.ntt.co.jp> <20190517153653.pmolnulev6imwsn3@momjian.us> From: Amit Langote Message-ID: <1edcf5e3-fca8-14d6-6c03-b57921c21cb8@lab.ntt.co.jp> Date: Tue, 21 May 2019 09:47:54 +0900 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20190517153653.pmolnulev6imwsn3@momjian.us> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-CC-Mail-RelayStamp: 1 To: Bruce Momjian Cc: David Rowley , "Jonathan S. Katz" , pgsql-advocacy@lists.postgresql.org X-TM-AS-MML: disable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2019/05/18 0:36, Bruce Momjian wrote: > On Fri, May 17, 2019 at 07:56:55PM +0900, Amit Langote wrote: >> I agree that the current description captures at a high level the many >> changes that made it possible. Although, a couple of commits listed with >> this item don't have much to do with that description, AFAICT. Especially >> 959d00e9d [1], which taught the planner to leverage the ordering imposed >> on partitions by range partitioning. With that commit, getting ordered >> output from partitioned tables is now much quicker, especially with a >> LIMIT clause. You can tell that it sounds clearly unrelated to the >> description we have now, which is "processing thousands of partitions is > > Yes, it does. I added this text and moved the commit item: > > Avoid sorting when partitions are already being scanned in the > necessary order (David Rowley) Thank you Bruce. Regards, Amit