agora inbox for [email protected]help / color / mirror / Atom feed
[PATCH 1/4] Improve CREATE TABLE documentation of partitioning 39+ messages / 2 participants [nested] [flat]
* [PATCH 1/4] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------89FC639615756AE2477DE3D6 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/3] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------76C2EB2C075826E6F80B02F0 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/3] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------76C2EB2C075826E6F80B02F0 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/4] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------89FC639615756AE2477DE3D6 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/3] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------76C2EB2C075826E6F80B02F0 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/3] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------76C2EB2C075826E6F80B02F0 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/4] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------89FC639615756AE2477DE3D6 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/3] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------76C2EB2C075826E6F80B02F0 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/4] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------89FC639615756AE2477DE3D6 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/4] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------89FC639615756AE2477DE3D6 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/4] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------89FC639615756AE2477DE3D6 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/3] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------76C2EB2C075826E6F80B02F0 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/4] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------89FC639615756AE2477DE3D6 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/3] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------76C2EB2C075826E6F80B02F0 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/4] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------89FC639615756AE2477DE3D6 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/3] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------76C2EB2C075826E6F80B02F0 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/3] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------76C2EB2C075826E6F80B02F0 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/4] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------89FC639615756AE2477DE3D6 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/4] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------89FC639615756AE2477DE3D6 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/4] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------89FC639615756AE2477DE3D6 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/3] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------76C2EB2C075826E6F80B02F0 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/4] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------89FC639615756AE2477DE3D6 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/3] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------76C2EB2C075826E6F80B02F0 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/4] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------89FC639615756AE2477DE3D6 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/3] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------76C2EB2C075826E6F80B02F0 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/4] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------89FC639615756AE2477DE3D6 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/3] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------76C2EB2C075826E6F80B02F0 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/3] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------76C2EB2C075826E6F80B02F0 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/4] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------89FC639615756AE2477DE3D6 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/3] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------76C2EB2C075826E6F80B02F0 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/4] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------89FC639615756AE2477DE3D6 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/3] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------76C2EB2C075826E6F80B02F0 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/4] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------89FC639615756AE2477DE3D6 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/4] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------89FC639615756AE2477DE3D6 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/3] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------76C2EB2C075826E6F80B02F0 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/4] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------89FC639615756AE2477DE3D6 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/3] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------76C2EB2C075826E6F80B02F0 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH 1/3] Improve CREATE TABLE documentation of partitioning @ 2017-01-26 09:57 amit <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: amit @ 2017-01-26 09:57 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 103 ++++++++++++++++++++++++++++++++++--- 1 file changed, 96 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 58f8bf6d6a..5596250aef 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -85,8 +85,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <phrase>and <replaceable class="PARAMETER">partition_bound_spec</replaceable> is:</phrase> -{ IN ( <replaceable class="PARAMETER">expression</replaceable> [, ...] ) | - FROM ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">expression</replaceable> | UNBOUNDED } [, ...] ) } +{ IN ( { <replaceable class="PARAMETER">bound_literal</replaceable> | NULL } [, ...] ) | + FROM ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) TO ( { <replaceable class="PARAMETER">bound_literal</replaceable> | UNBOUNDED } [, ...] ) } <phrase><replaceable class="PARAMETER">index_parameters</replaceable> in <literal>UNIQUE</literal>, <literal>PRIMARY KEY</literal>, and <literal>EXCLUDE</literal> constraints are:</phrase> @@ -261,6 +261,44 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> + <note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that can be + automatically coerced to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper bound + specified with <literal>TO</literal> is an exclusive bound. That is, + the values specified in the <literal>FROM</literal> list are accepted + values of the corresponding partition key columns in a given partition, + whereas those in the <literal>TO</literal> list are not. To be precise, + this applies only to the first of the partition key columns for which + the corresponding values in the <literal>FROM</literal> and + <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> 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. <literal>NULL</literal> cannot specified for range + partitions. + </para> + </note> + <para> A partition cannot have columns other than those inherited from the parent. That includes the <structfield>oid</> column, which can be @@ -386,11 +424,12 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <firstterm>partitioned</firstterm> table. The parenthesized list of columns or expressions forms the <firstterm>partition key</firstterm> for the table. When using range partitioning, the partition key can - include multiple columns or expressions, but for list partitioning, the - partition key must consist of a single column or expression. If no - btree operator class is specified when creating a partitioned table, - the default btree operator class for the datatype will be used. If - there is none, an error will be reported. + include multiple columns or expressions (up to 32, but this limit can + altered when building <productname>PostgreSQL</productname>.), but for + list partitioning, the partition key must consist of a single column or + expression. If no btree operator class is specified when creating a + partitioned table, the default btree operator class for the datatype will + be used. If there is none, an error will be reported. </para> <para> @@ -1485,6 +1524,16 @@ CREATE TABLE measurement ( </programlisting></para> <para> + Create a range partitioned table with multiple columns in the partition key: +<programlisting> +CREATE TABLE measurement_year_month ( + logdate date not null, + peaktemp int, + unitsales int +) PARTITION BY RANGE (EXTRACT(YEAR FROM DATE logdate), EXTRACT(MONTH FROM DATE logdate)); +</programlisting></para> + + <para> Create a list partitioned table: <programlisting> CREATE TABLE cities ( @@ -1504,6 +1553,27 @@ CREATE TABLE measurement_y2016m07 </programlisting></para> <para> + Create a few partitions of a range partitioned table with multiple + columns in the partition key: +<programlisting> +CREATE TABLE measurement_ym_older + PARTITION OF measurement_year_month + FOR VALUES FROM (unbounded, unbounded) TO (2016, 11); + +CREATE TABLE measurement_ym_y2016m11 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 11) TO (2016, 12); + +CREATE TABLE measurement_ym_y2016m12 + PARTITION OF measurement_year_month + FOR VALUES FROM (2016, 12) TO (2017, 01); + +CREATE TABLE measurement_ym_y2017m01 + PARTITION OF measurement_year_month + FOR VALUES FROM (2017, 01) TO (2017, 02); +</programlisting></para> + + <para> Create partition of a list partitioned table: <programlisting> CREATE TABLE cities_ab @@ -1705,6 +1775,25 @@ CREATE TABLE cities_ab_10000_to_100000 effect can be had using the OID feature. </para> </refsect2> + + <refsect2> + <title><literal>PARTITION BY</> Clause</title> + + <para> + The <literal>PARTITION BY</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + + <refsect2> + <title><literal>PARTITION OF</> Clause</title> + + <para> + The <literal>PARTITION OF</> clause is a + <productname>PostgreSQL</productname> extension. + </para> + </refsect2> + </refsect1> -- 2.11.0 --------------76C2EB2C075826E6F80B02F0 Content-Type: text/x-diff; name="0002-Update-ddl.sgml-for-declarative-partitioning.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Update-ddl.sgml-for-declarative-partitioning.patch" ^ permalink raw reply [nested|flat] 39+ messages in thread
* [PATCH v29 02/11] Add relisivm column to pg_class system catalog @ 2019-12-20 01:07 Yugo Nagata <[email protected]> 0 siblings, 0 replies; 39+ messages in thread From: Yugo Nagata @ 2019-12-20 01:07 UTC (permalink / raw) If this boolean column is true, a relations is Incrementally Maintainable Materialized View (IMMV). This is set when IMMV is created. Also, isimmv columns is added to pg_matviews system view. isimmv --- src/backend/catalog/heap.c | 1 + src/backend/catalog/index.c | 1 + src/backend/catalog/system_views.sql | 1 + src/backend/utils/cache/lsyscache.c | 24 ++++++++++++++++++++++++ src/backend/utils/cache/relcache.c | 2 ++ src/include/catalog/pg_class.h | 3 +++ src/include/utils/lsyscache.h | 1 + src/include/utils/rel.h | 2 ++ src/test/regress/expected/rules.out | 1 + 9 files changed, 36 insertions(+) diff --git a/src/backend/catalog/heap.c b/src/backend/catalog/heap.c index b534da7d80..d9eac41463 100644 --- a/src/backend/catalog/heap.c +++ b/src/backend/catalog/heap.c @@ -924,6 +924,7 @@ InsertPgClassTuple(Relation pg_class_desc, values[Anum_pg_class_relrewrite - 1] = ObjectIdGetDatum(rd_rel->relrewrite); values[Anum_pg_class_relfrozenxid - 1] = TransactionIdGetDatum(rd_rel->relfrozenxid); values[Anum_pg_class_relminmxid - 1] = MultiXactIdGetDatum(rd_rel->relminmxid); + values[Anum_pg_class_relisivm - 1] = BoolGetDatum(rd_rel->relisivm); if (relacl != (Datum) 0) values[Anum_pg_class_relacl - 1] = relacl; else diff --git a/src/backend/catalog/index.c b/src/backend/catalog/index.c index fd09378848..e4b52fdd21 100644 --- a/src/backend/catalog/index.c +++ b/src/backend/catalog/index.c @@ -993,6 +993,7 @@ index_create(Relation heapRelation, indexRelation->rd_rel->relowner = heapRelation->rd_rel->relowner; indexRelation->rd_rel->relam = accessMethodId; indexRelation->rd_rel->relispartition = OidIsValid(parentIndexRelid); + indexRelation->rd_rel->relisivm = false; /* * store index's pg_class entry diff --git a/src/backend/catalog/system_views.sql b/src/backend/catalog/system_views.sql index 77b06e2a7a..2b60ed9e52 100644 --- a/src/backend/catalog/system_views.sql +++ b/src/backend/catalog/system_views.sql @@ -146,6 +146,7 @@ CREATE VIEW pg_matviews AS T.spcname AS tablespace, C.relhasindex AS hasindexes, C.relispopulated AS ispopulated, + C.relisivm AS isimmv, pg_get_viewdef(C.oid) AS definition FROM pg_class C LEFT JOIN pg_namespace N ON (N.oid = C.relnamespace) LEFT JOIN pg_tablespace T ON (T.oid = C.reltablespace) diff --git a/src/backend/utils/cache/lsyscache.c b/src/backend/utils/cache/lsyscache.c index fc6d267e44..2b29ab4409 100644 --- a/src/backend/utils/cache/lsyscache.c +++ b/src/backend/utils/cache/lsyscache.c @@ -2046,6 +2046,30 @@ get_rel_relispartition(Oid relid) return false; } +/* + * get_rel_relisivm + * + * Returns the relisivm flag associated with a given relation. + */ +bool +get_rel_relisivm(Oid relid) +{ + HeapTuple tp; + + tp = SearchSysCache1(RELOID, ObjectIdGetDatum(relid)); + if (HeapTupleIsValid(tp)) + { + Form_pg_class reltup = (Form_pg_class) GETSTRUCT(tp); + bool result; + + result = reltup->relisivm; + ReleaseSysCache(tp); + return result; + } + else + return false; +} + /* * get_rel_tablespace * diff --git a/src/backend/utils/cache/relcache.c b/src/backend/utils/cache/relcache.c index 7234cb3da6..96cd510780 100644 --- a/src/backend/utils/cache/relcache.c +++ b/src/backend/utils/cache/relcache.c @@ -1924,6 +1924,8 @@ formrdesc(const char *relationName, Oid relationReltype, /* ... and they're always populated, too */ relation->rd_rel->relispopulated = true; + /* ... and they're always no ivm, too */ + relation->rd_rel->relisivm = false; relation->rd_rel->relreplident = REPLICA_IDENTITY_NOTHING; relation->rd_rel->relpages = 0; diff --git a/src/include/catalog/pg_class.h b/src/include/catalog/pg_class.h index 2d1bb7af3a..62b9c0e5cb 100644 --- a/src/include/catalog/pg_class.h +++ b/src/include/catalog/pg_class.h @@ -119,6 +119,9 @@ CATALOG(pg_class,1259,RelationRelationId) BKI_BOOTSTRAP BKI_ROWTYPE_OID(83,Relat /* is relation a partition? */ bool relispartition BKI_DEFAULT(f); + /* is relation a matview with ivm? */ + bool relisivm BKI_DEFAULT(f); + /* link to original rel during table rewrite; otherwise 0 */ Oid relrewrite BKI_DEFAULT(0) BKI_LOOKUP_OPT(pg_class); diff --git a/src/include/utils/lsyscache.h b/src/include/utils/lsyscache.h index f5fdbfe116..7b433749f5 100644 --- a/src/include/utils/lsyscache.h +++ b/src/include/utils/lsyscache.h @@ -138,6 +138,7 @@ extern Oid get_rel_namespace(Oid relid); extern Oid get_rel_type_id(Oid relid); extern char get_rel_relkind(Oid relid); extern bool get_rel_relispartition(Oid relid); +extern bool get_rel_relisivm(Oid relid); extern Oid get_rel_tablespace(Oid relid); extern char get_rel_persistence(Oid relid); extern Oid get_transform_fromsql(Oid typid, Oid langid, List *trftypes); diff --git a/src/include/utils/rel.h b/src/include/utils/rel.h index 1426a353cd..b8961176bb 100644 --- a/src/include/utils/rel.h +++ b/src/include/utils/rel.h @@ -677,6 +677,8 @@ RelationCloseSmgr(Relation relation) */ #define RelationIsPopulated(relation) ((relation)->rd_rel->relispopulated) +#define RelationIsIVM(relation) ((relation)->rd_rel->relisivm) + /* * RelationIsAccessibleInLogicalDecoding * True if we need to log enough information to have access via diff --git a/src/test/regress/expected/rules.out b/src/test/regress/expected/rules.out index 5058be5411..cc5287344d 100644 --- a/src/test/regress/expected/rules.out +++ b/src/test/regress/expected/rules.out @@ -1392,6 +1392,7 @@ pg_matviews| SELECT n.nspname AS schemaname, t.spcname AS tablespace, c.relhasindex AS hasindexes, c.relispopulated AS ispopulated, + c.relisivm AS isimmv, pg_get_viewdef(c.oid) AS definition FROM ((pg_class c LEFT JOIN pg_namespace n ON ((n.oid = c.relnamespace))) -- 2.25.1 --Multipart=_Mon__28_Aug_2023_16_05_30_+0900_b1OvQD_3A3ZMTGvj Content-Type: text/x-diff; name="v29-0003-Allow-to-prolong-life-span-of-transition-tables-.patch" Content-Disposition: attachment; filename="v29-0003-Allow-to-prolong-life-span-of-transition-tables-.patch" Content-Transfer-Encoding: 7bit ^ permalink raw reply [nested|flat] 39+ messages in thread
end of thread, other threads:[~2019-12-20 01:07 UTC | newest] Thread overview: 39+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2017-01-26 09:57 [PATCH 1/4] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/3] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/3] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/4] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/3] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/4] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/4] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/4] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/3] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/3] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/3] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/3] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/4] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/4] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/4] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/4] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/3] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/4] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/4] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/3] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/3] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/3] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/3] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/4] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/4] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/3] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/3] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/4] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/3] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/4] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/4] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/3] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/4] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/4] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/3] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/3] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/4] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2017-01-26 09:57 [PATCH 1/3] Improve CREATE TABLE documentation of partitioning amit <[email protected]> 2019-12-20 01:07 [PATCH v29 02/11] Add relisivm column to pg_class system catalog Yugo Nagata <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox