<term><literal>VALUES LESS THAN (<replaceable class="PARAMETER">value</replaceable>)</literal></term>

<listitem>

<para>

Thisform specifies the range of values to include into a single partition. The specified <literal>value</literal> is not included into the created partition.

Thisclause specifies the range of values to include into a single partition. The specified <replaceable>value</replaceable> is not included into the created partition.

</para>

</listitem>

</varlistentry>

<term><literal>TABLESPACE <replaceable class="PARAMETER">tablespace_name</replaceable></literal></term>

<listitem>

<para>

Thisform specifies the name of the tablespace to which the created partition will belong.

Thisclause specifies the name of the tablespace to which the created partition will belong.

If not specified, <xref linkend="guc-default-tablespace"> is consulted.

</para>

</listitem>

<varlistentry>

<term><literal>SPLIT PARTITION <replaceable class="PARAMETER">partition_name</replaceable></literal></term>

<listitem><para>This form separates a range partition into two based on the value provided in the <literal>AT</literal>form.

<listitem><para>This form separates a range partition into two based on the value provided in the <literal>AT</literal>clause.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term><literal>AT (<replaceable class="PARAMETER">value</replaceable>)</literal></term>

<listitem><para>Thisform specifies the value by which to split a range partition. The provided value serves as the lower bound of thesecond partition.

<listitem><para>Thisclause specifies the value by which to split a range partition. The provided value serves as the lower bound of theright partition.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term><literal>INTO</literal></term>

<listitem><para>Thisform specifies one or more target partitions. Use thisform when performing <literal>SPLIT</literal> and <literal>MERGE</literal> actions. If you omit thisform when splitting partitions, the left partition will use the parent partion name, and the right partition name will be generated automatically.

<listitem><para>Thisclause specifies one or more target partitions. Use thisclause when performing <literal>SPLIT</literal> and <literal>MERGE</literal> actions. If you omit thisclause when splitting partitions, the left partition will use the parent partion name, and the right partition name will be generated automatically.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term><literal>RENAME PARTITION <replaceable class="PARAMETER">partition_name</replaceable></literal></term>

<listitem><para>This form renames a partition. The new partition name must be specified in the <literal>TO</literal>form.

<listitem><para>This form renames a partition. The new partition name must be specified in the <literal>TO</literal>clause.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term><literal>TO <replaceable class="PARAMETER">new_partition_name</replaceable></literal></term>

<listitem><para>Thisform specifies a new partition name.

<listitem><para>Thisclause specifies a new partition name.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term><literal>MOVE PARTITION <replaceable class="PARAMETER">partition_name</replaceable></literal></term>

<listitem><para>This form moves the partition to a different tablespace specified in the <literal>TABLESPACE</literal>form.

<listitem><para>This form moves the partition to a different tablespace specified in the <literal>TABLESPACE</literal>clause.

</para>

</listitem>

</varlistentry>

<term><literal>PARTITION BY</literal></term>

<listitem>

<para>

Thisclause splits the created table into partitions based on the specified partitioning options.

Thisform splits the created table into partitions based on the specified partitioning options.

The supported partitioning options are:</para>

<variablelist>

<term><literal>PARTITIONS <replaceable class="PARAMETER">partition_count</replaceable></literal></term>

<listitem>

<para>

Specify the number of partitions to create with hash partitioning. Alternatively, you can specify the exact partitions to create using <literal>PARTITION</literal> option.

Specify the number of partitions to create with hash partitioning.

</para>

</listitem>

</varlistentry>

<term><literal>START FROM (<replaceable class="PARAMETER">start_value</replaceable>)</literal></term>

<listitem>

<para>

Specify the lower bound of the first partition to create. The <literal>start_value</literal> must be not greater than the smallest value in the partitioning key column. Otherwise, <filename>pg_pathman</filename> returns the corresponding error.

Specify the lower bound of the first partition to create. The <replaceable>start_value</replaceable> must be not greater than the smallest value in the partitioning key column. Otherwise, <filename>pg_pathman</filename> returns the corresponding error.

</para>

</listitem>

</varlistentry>

<term><literal>INTERVAL <replaceable class="PARAMETER">interval</replaceable></literal></term>

<listitem>

<para>

Specify the interval for range partitioning. When you insert data outside of the existing data range, all new partitions will be created with this interval.You can omit this option if you specify the exact partitions to create using the <literal>PARTITION</literal> option.If the <literal>INTERVAL</literal> is not specified, <filename>pg_pathman</filename> cannot create new partitions automatically. You can later use the <literal>SET INTERVAL</literal> form to enable automatic partition creation.

Specify the interval for range partitioning. When you insert data outside of the existing data range, all new partitions will be created with this interval. If the <literal>INTERVAL</literal> is not specified, <filename>pg_pathman</filename> cannot create new partitions automatically. You can later use the <literal>SET INTERVAL</literal> form to enable automatic partition creation.

</para>

</listitem>

</varlistentry>

<para>

All the forms of ALTER TABLE that act on a single table, except

<literal>RENAME</literal>, and <literal>SET SCHEMA</literal>

can be combined into a list of multiple alterations to applied together.

<literal>RENAME</literal>,<literal>PARTITION BY</literal>,and <literal>SET SCHEMA</literal>,

can be combined into a list of multiple alterations tobeapplied together.

For example, it

is possible to add several columns and/or alter the type of several

columns in a single command. This is particularly useful with large

index on the column or group of columns used in the constraint.

Optional clause <literal>INCLUDE</literal> allows to add into the index

a portion of columns on which the uniqueness is not enforced upon.

Note, thatalthogh constraint is not enforced upon included columns, it still

Note, thatalthough constraint is not enforced upon included columns, it still

depends on them. Consequently, some operations on these columns (e.g. <literal>DROP COLUMN</literal>)

can cause cascade constraint and index deletion.

See paragraph about <literal>INCLUDE</literal> in

index on the column or group of columns used in the constraint.

An optional clause <literal>INCLUDE</literal> allows to add into the index

a portion of columns on which the constraint is not enforced upon.

Note, thatalthogh constraint is not enforced upon included columns, it still

Note, thatalthough constraint is not enforced upon included columns, it still

depends on them. Consequently, some operations on these columns (e.g. <literal>DROP COLUMN</literal>)

can cause cascade constraint and index deletion.

See paragraph about <literal>INCLUDE</literal> in