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 1hQhsS-0006NE-Oq for pgsql-advocacy@arkaria.postgresql.org; Wed, 15 May 2019 00:34: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 1hQhsQ-0005C2-CU for pgsql-advocacy@arkaria.postgresql.org; Wed, 15 May 2019 00:34:34 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1hQhsQ-0005Bv-55 for pgsql-advocacy@lists.postgresql.org; Wed, 15 May 2019 00:34:34 +0000 Received: from tama500.ecl.ntt.co.jp ([129.60.39.148]) by magus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hQhsH-0004Ij-L8 for pgsql-advocacy@lists.postgresql.org; Wed, 15 May 2019 00:34:33 +0000 Received: from vc2.ecl.ntt.co.jp (vc2.ecl.ntt.co.jp [129.60.86.154]) by tama500.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id x4F0YJ7b019222; Wed, 15 May 2019 09:34:19 +0900 Received: from vc2.ecl.ntt.co.jp (localhost [127.0.0.1]) by vc2.ecl.ntt.co.jp (Postfix) with ESMTP id CE5926387C4; Wed, 15 May 2019 09:34:19 +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 C202B638078; Wed, 15 May 2019 09:34:19 +0900 (JST) Received: from [127.0.0.1] (unknown [129.60.241.61]) by jcms-pop21.ecl.ntt.co.jp (Postfix) with ESMTPSA id B605E40078A; Wed, 15 May 2019 09:34:19 +0900 (JST) Subject: Re: PostgreSQL 12: Feature Highlights References: <830415f7-78ec-ef7b-0f73-0e810ef87f91@postgresql.org> <3ea29ec1-38e9-b5bd-571e-8d1f85175c5a@lab.ntt.co.jp> <20190514025918.mqfedp3k625t5eoc@momjian.us> <20190514131945.6dof67bfzmcftevd@momjian.us> From: Amit Langote Message-ID: <8fd9a06a-8d8f-b943-0ac1-7a4d58e7b20c@lab.ntt.co.jp> Date: Wed, 15 May 2019 09:34:10 +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: <20190514131945.6dof67bfzmcftevd@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 , Justin Clift , "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/14 22:19, Bruce Momjian wrote: > On Tue, May 14, 2019 at 06:25:43PM +0900, Amit Langote wrote: >> Considering the quoted discussion here, maybe it's a good idea to note >> that only the operations that need to touch a small number of partitions >> are now processed efficiently, which covers both SELECT/UPDATE/DELETE that >> benefit from improved pruning efficiency and INSERT that benefit from >> improved tuple routing efficiency. So, maybe: >> >> Tables with thousands of child partitions can now be processed >> efficiently by operations that only need to touch a small number >> of partitions. >> >> That is, as I mentioned above, as opposed to queries that need to process >> all partitions (such as, select count(*) from partitioned_table), which >> don't perform any faster in v12 than in v11. The percentage of users who >> run such workloads on PostgreSQL may be much smaller today, but perhaps >> it's not a good idea to mislead them into thinking that *everything* with >> partitioned tables is now faster even with thousands of partitions. > > Agreed, I changed it to your wording. Thank you. Regards, Amit