diff options
| author | Robert Haas <rhaas@postgresql.org> | 2017-12-11 12:48:40 -0500 |
|---|---|---|
| committer | Robert Haas <rhaas@postgresql.org> | 2017-12-11 12:52:15 -0500 |
| commit | 01a0ca1bed02d6a375c6565a529555eefd2b4fe8 (patch) | |
| tree | 356c3a44b56ecaf8dc7878599919b3e212a6eae4 | |
| parent | 9edc97b712e2f0ba041b40b4b2e2285d229f4fb0 (diff) | |
| download | postgresql-01a0ca1bed02d6a375c6565a529555eefd2b4fe8.tar.gz postgresql-01a0ca1bed02d6a375c6565a529555eefd2b4fe8.zip | |
Improve comment about PartitionBoundInfoData.
Ashutosh Bapat, per discussion with Julien Rouhaund, who also
reviewed this patch.
Discussion: http://postgr.es/m/CAFjFpReBR3ftK9C23LLCZY_TDXhhjB_dgE-L9+mfTnA=gkvdvQ@mail.gmail.com
| -rw-r--r-- | src/backend/catalog/partition.c | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/src/backend/catalog/partition.c b/src/backend/catalog/partition.c index dd4a8d3c02d..ef156e449e5 100644 --- a/src/backend/catalog/partition.c +++ b/src/backend/catalog/partition.c @@ -72,6 +72,13 @@ * of datum-tuples with 2 datums, modulus and remainder, corresponding to a * given partition. * + * The datums in datums array are arranged in increasing order as defined by + * functions qsort_partition_rbound_cmp(), qsort_partition_list_value_cmp() and + * qsort_partition_hbound_cmp() for range, list and hash partitioned tables + * respectively. For range and list partitions this simply means that the + * datums in the datums array are arranged in increasing order as defined by + * the partition key's operator classes and collations. + * * In the case of list partitioning, the indexes array stores one entry for * every datum, which is the index of the partition that accepts a given datum. * In case of range partitioning, it stores one entry per distinct range |