diff options
| -rw-r--r-- | doc/src/sgml/ref/alter_table.sgml | 4 | ||||
| -rw-r--r-- | doc/src/sgml/ref/create_table.sgml | 25 | ||||
| -rw-r--r-- | doc/src/sgml/ref/insert.sgml | 11 | ||||
| -rw-r--r-- | doc/src/sgml/ref/update.sgml | 8 |
4 files changed, 34 insertions, 14 deletions
diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml index a6a43c4b302..333b01db36e 100644 --- a/doc/src/sgml/ref/alter_table.sgml +++ b/doc/src/sgml/ref/alter_table.sgml @@ -715,7 +715,7 @@ ALTER TABLE [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> </varlistentry> <varlistentry> - <term><literal>ATTACH PARTITION</literal> <replaceable class="PARAMETER">partition_name</replaceable> <replaceable class="PARAMETER">partition_bound_spec</replaceable></term> + <term><literal>ATTACH PARTITION</literal> <replaceable class="PARAMETER">partition_name</replaceable> FOR VALUES <replaceable class="PARAMETER">partition_bound_spec</replaceable></term> <listitem> <para> This form attaches an existing table (which might itself be partitioned) @@ -1332,7 +1332,7 @@ ALTER TABLE measurement Attach a partition to list partitioned table: <programlisting> ALTER TABLE cities - ATTACH PARTITION cities_west FOR VALUES IN ('Los Angeles', 'San Francisco'); + ATTACH PARTITION cities_ab FOR VALUES IN ('a', 'b'); </programlisting></para> <para> diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 8bf8af302b5..58f8bf6d6a1 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -248,7 +248,7 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI </varlistentry> <varlistentry> - <term><literal>PARTITION OF <replaceable class="PARAMETER">parent_table</replaceable></literal></term> + <term><literal>PARTITION OF <replaceable class="PARAMETER">parent_table</replaceable></literal> FOR VALUES <replaceable class="PARAMETER">partition_bound_spec</replaceable></term> <listitem> <para> Creates the table as <firstterm>partition</firstterm> of the specified @@ -275,7 +275,8 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI <para> Rows inserted into a partitioned table will be automatically routed to the correct partition. If no suitable partition exists, an error will - occur. + occur. Also, if updating a row in a given partition causes it to move + to another partition due to the new partition key, an error will occur. </para> <para> @@ -1477,7 +1478,6 @@ CREATE TABLE employees OF employee_type ( Create a range partitioned table: <programlisting> CREATE TABLE measurement ( - city_id int not null, logdate date not null, peaktemp int, unitsales int @@ -1488,9 +1488,10 @@ CREATE TABLE measurement ( Create a list partitioned table: <programlisting> CREATE TABLE cities ( + city_id bigserial not null, name text not null, - population int, -) PARTITION BY LIST (initcap(name)); + population bigint, +) PARTITION BY LIST (left(lower(name), 1)); </programlisting></para> <para> @@ -1498,30 +1499,30 @@ CREATE TABLE cities ( <programlisting> CREATE TABLE measurement_y2016m07 PARTITION OF measurement ( - unitsales WITH OPTIONS DEFAULT 0 + unitsales DEFAULT 0 ) FOR VALUES FROM ('2016-07-01') TO ('2016-08-01'); </programlisting></para> <para> Create partition of a list partitioned table: <programlisting> -CREATE TABLE cities_west +CREATE TABLE cities_ab PARTITION OF cities ( CONSTRAINT city_id_nonzero CHECK (city_id != 0) -) FOR VALUES IN ('Los Angeles', 'San Francisco'); +) FOR VALUES IN ('a', 'b'); </programlisting></para> <para> Create partition of a list partitioned table that is itself further partitioned and then add a partition to it: <programlisting> -CREATE TABLE cities_west +CREATE TABLE cities_ab PARTITION OF cities ( CONSTRAINT city_id_nonzero CHECK (city_id != 0) -) FOR VALUES IN ('Los Angeles', 'San Francisco') PARTITION BY RANGE (population); +) FOR VALUES IN ('a', 'b') PARTITION BY RANGE (population); -CREATE TABLE cities_west_10000_to_100000 - PARTITION OF cities_west FOR VALUES FROM (10000) TO (100000); +CREATE TABLE cities_ab_10000_to_100000 + PARTITION OF cities_ab FOR VALUES FROM (10000) TO (100000); </programlisting></para> </refsect1> diff --git a/doc/src/sgml/ref/insert.sgml b/doc/src/sgml/ref/insert.sgml index 06f416039b9..00c984d8d54 100644 --- a/doc/src/sgml/ref/insert.sgml +++ b/doc/src/sgml/ref/insert.sgml @@ -526,6 +526,17 @@ INSERT <replaceable>oid</replaceable> <replaceable class="parameter">count</repl updated by the command. </para> </refsect1> + + <refsect1> + <title>Notes</title> + + <para> + If the specified table is a partitioned table, each row is routed to + the appropriate partition and inserted into it. If the specified table + is a partition, an error will occur if one of the input rows violates + the partition constraint. + </para> + </refsect1> <refsect1> <title>Examples</title> diff --git a/doc/src/sgml/ref/update.sgml b/doc/src/sgml/ref/update.sgml index 2de0f4aad10..8a1619fb68b 100644 --- a/doc/src/sgml/ref/update.sgml +++ b/doc/src/sgml/ref/update.sgml @@ -279,6 +279,14 @@ UPDATE <replaceable class="parameter">count</replaceable> sub-selects is safer, though often harder to read and slower than using a join. </para> + + <para> + In the case of a partitioned table, updating a row might cause it to no + longer satisfy the partition constraint. Since there is no provision to + move the row to the partition appropriate to the new value of its + partitioning key, an error will occur in this case. This can also happen + when updating a partition directly. + </para> </refsect1> <refsect1> |