Re: Partitioning docs (was Re: Range partitioning and overlap)
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Pg Docs <pgsql-docs@lists.postgresql.org>,
Edson Richter <edsonrichter@hotmail.com>
Date: 2020-11-14T18:11:29Z
Lists: pgsql-general, pgsql-docs
I wrote: > "David G. Johnston" <david.g.johnston@gmail.com> 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
Commits
-
Doc: improve partitioning discussion in ddl.sgml.
- dbca94510c9e 14.0 landed
- a87d7801c24f 11.11 landed
- 2b7759508542 12.6 landed
- 0e0e71abdcae 13.2 landed