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 1kdm2e-0008Qk-RZ for pgsql-docs@arkaria.postgresql.org; Sat, 14 Nov 2020 03:15:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kdm2d-0004P5-Py for pgsql-docs@arkaria.postgresql.org; Sat, 14 Nov 2020 03:15:55 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kdm2d-0004Ow-Ka for pgsql-docs@lists.postgresql.org; Sat, 14 Nov 2020 03:15:55 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kdm2a-000884-La for pgsql-docs@lists.postgresql.org; Sat, 14 Nov 2020 03:15:54 +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 0AE3FmBU417735; Fri, 13 Nov 2020 22:15:48 -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: References: <398613.1605301084@sss.pgh.pa.us> <414580.1605320014@sss.pgh.pa.us> Comments: In-reply-to "David G. Johnston" message dated "Fri, 13 Nov 2020 19:43:00 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <417733.1605323748.1@sss.pgh.pa.us> Date: Fri, 13 Nov 2020 22:15:48 -0500 Message-ID: <417734.1605323748@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk "David G. Johnston" writes: > Looks good to me (just read the patch), Thanks! Just one suggestion toward > the top: > ...allows you to (specify declaratively => declare) that a table is divided > into partitions. (specification becomes declaration further down) Sure. That's a little further from the previous wording than what I had, but it's probably better. > 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]