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 1ke01S-0002TT-Pk for pgsql-docs@arkaria.postgresql.org; Sat, 14 Nov 2020 18:11:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ke01R-0007Cm-Mg for pgsql-docs@arkaria.postgresql.org; Sat, 14 Nov 2020 18:11:37 +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 1ke01R-0007BZ-HD for pgsql-docs@lists.postgresql.org; Sat, 14 Nov 2020 18:11:37 +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 1ke01P-0002e3-G0 for pgsql-docs@lists.postgresql.org; Sat, 14 Nov 2020 18:11:37 +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 0AEIBTYX469468; Sat, 14 Nov 2020 13:11:29 -0500 From: Tom Lane To: "David G. Johnston" cc: Pg Docs , Edson Richter Subject: Re: Partitioning docs (was Re: Range partitioning and overlap) In-reply-to: <417734.1605323748@sss.pgh.pa.us> References: <398613.1605301084@sss.pgh.pa.us> <414580.1605320014@sss.pgh.pa.us> <417734.1605323748@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Fri, 13 Nov 2020 22:15:48 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <469466.1605377489.1@sss.pgh.pa.us> Date: Sat, 14 Nov 2020 13:11:29 -0500 Message-ID: <469467.1605377489@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk I wrote: > "David G. Johnston" writes: >> I am curious as to your thoughts on unique indexes and whether/how to >> better incorporate advice regarding the use of ON CONFLICT with >> partitioning [1] vis-a-vis the overview's claim of: >> "The partitioning substitutes for leading columns of indexes, reducing >> index size and making it more likely that the heavily-used parts of the >> indexes fit in memory" [2] > Possibly a better way to write that claim is that partitioning can > substitute for the upper levels of a huge index, rather than "leading > columns" per se. That way of looking at it is still sensible when > a partition covers more than one value of the key column. I changed it like that and pushed. regards, tom lane