Vertica Analytics Platform Version 9.2.x Documentation

DROP_PARTITIONS

This function supersedes meta-function DROP_PARTITION. Vertica will continue to support DROP_PARTITION. For information about DROP PARTITION, refer to the Vertica 8.1.x documentation.

Drops the specified table partition keys. If the WOS contains table data, DROP_PARTITIONS forces a moveout before it executes the drop operation.

Syntax

DROP_PARTITIONS (
    '[[database.]schema.]table‑name',
    'min‑range‑value',
    'max‑range‑value' 
    [, 'force‑split']
)

Parameters

[database.]schema

Specifies a schema, by default public. If schema is any schema other than public, you must supply the schema name. For example:

myschema.thisDbObject

If you specify a database, it must be the current database.

table‑name

The target table. The table cannot be used as a dimension table in a pre-join projection and cannot have out-of-date (unrefreshed) projections.

min‑range‑value
max‑range‑value
The minimum and maximum value of partition keys to drop, where min‑range‑value must be ≤ max‑range‑value. To drop one partition key, min‑range‑value and max‑range‑value must be equal.
force‑split

Optional Boolean argument, specifies whether to split ROS containers if the range of partition keys spans multiple containers or part of a single container:

  • true: Split ROS containers as needed.
  • false (default): Return with an error if ROS containers must be split to implement this operation.

Privileges

One of the following:

  • DBADMIN
  • Table owner
  • USAGE privileges on the table schema and TRUNCATE privileges on the table

Examples

See Dropping Partitions in the Administrator's Guide.

See Also

PARTITION_TABLE