</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)

Attach a partition to list partitioned table:

<programlisting>

ALTER TABLE cities

ATTACH PARTITIONcities_west FOR VALUES IN ('Los Angeles', 'San Francisco');

ATTACH PARTITIONcities_ab FOR VALUES IN ('a', 'b');

</programlisting></para>

<para>

</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

<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>

Create a range partitioned table:

<programlisting>

CREATE TABLE measurement (

city_id int not null,

logdate date not null,

peaktemp int,

unitsales int

Create a list partitioned table:

<programlisting>

CREATE TABLE cities (

city_id bigserial not null,

name text not null,

populationint,

) PARTITION BY LIST (initcap(name));

populationbigint,

) PARTITION BY LIST (left(lower(name), 1));

</programlisting></para>

<para>

Create partition of a range partitioned table:

<programlisting>

CREATE TABLE measurement_y2016m07

PARTITION OF measurement (

unitsalesWITH OPTIONSDEFAULT 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 TABLEcities_west

CREATE TABLEcities_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 TABLEcities_west

CREATE TABLEcities_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 TABLEcities_west_10000_to_100000

PARTITION OFcities_west FOR VALUES FROM (10000) TO (100000);

CREATE TABLEcities_ab_10000_to_100000

PARTITION OFcities_ab FOR VALUES FROM (10000) TO (100000);

</programlisting></para>

</refsect1>

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>

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>