From 02c8753b3a81589c5f6679bcc4d50f452d0c658d Mon Sep 17 00:00:00 2001 From: amit Date: Mon, 27 Feb 2017 19:00:08 +0900 Subject: [PATCH 3/3] Listify a note on the CREATE TABLE page --- doc/src/sgml/ref/create_table.sgml | 82 ++++++++++++++++++++++---------------- 1 file changed, 47 insertions(+), 35 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..161f7d1280 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -262,41 +262,53 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI - - Each of the values specified in the partition bound specification is - a literal, NULL, or UNBOUNDED. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - - - - When creating a range partition, the lower bound specified with - FROM is an inclusive bound, whereas the upper bound - specified with TO is an exclusive bound. That is, - the values specified in the FROM list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the TO list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the FROM and - TO lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in FROM and TO - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying UNBOUNDED in FROM - signifies -infinity as the lower bound of the - corresponding column, whereas it signifies +infinity - as the upper bound when specified in TO. - - - - When creating a list partition, NULL can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. NULL cannot specified for range - partitions. - + + + + Each of the values specified in the partition bound specification is + a literal, NULL, or UNBOUNDED. + A literal is either a numeric constant or a string constant that is + coercable to the corresponding partition key column's type. + + + + + + When creating a range partition, the lower bound specified with + FROM is an inclusive bound, whereas the upper + bound specified with TO is an exclusive bound. + That is, the values specified in the FROM list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the TO list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the FROM + and TO lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in FROM and TO + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + + + + + Specifying UNBOUNDED in FROM + signifies -infinity as the lower bound of the + corresponding column, whereas it signifies +infinity + as the upper bound when specified in TO. + + + + + + When creating a list partition, NULL can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. NULL + cannot specified for range partitions. + + + -- 2.11.0