Commit01a0ca1

committed

Improve comment about PartitionBoundInfoData.

Ashutosh Bapat, per discussion with Julien Rouhaund, who alsoreviewed this patch.Discussion:http://postgr.es/m/CAFjFpReBR3ftK9C23LLCZY_TDXhhjB_dgE-L9+mfTnA=gkvdvQ@mail.gmail.com

1 parent9edc97b commit01a0ca1Copy full SHA for 01a0ca1

File tree

-0

lines changed

-0

lines changed

Lines changed: 7 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -72,6 +72,13 @@`
`72`	`72`	`* of datum-tuples with 2 datums, modulus and remainder, corresponding to a`
`73`	`73`	`* given partition.`
`74`	`74`	`*`
	`75`	`+ * The datums in datums array are arranged in increasing order as defined by`
	`76`	`+ * functions qsort_partition_rbound_cmp(), qsort_partition_list_value_cmp() and`
	`77`	`+ * qsort_partition_hbound_cmp() for range, list and hash partitioned tables`
	`78`	`+ * respectively. For range and list partitions this simply means that the`
	`79`	`+ * datums in the datums array are arranged in increasing order as defined by`
	`80`	`+ * the partition key's operator classes and collations.`
	`81`	`+ *`
`75`	`82`	`* In the case of list partitioning, the indexes array stores one entry for`
`76`	`83`	`* every datum, which is the index of the partition that accepts a given datum.`
`77`	`84`	`* In case of range partitioning, it stores one entry per distinct range`

Comments

(0)