pg_pathman*.sqllinguist-vendored=true

*.hlinguist-language=C

*.clinguist-language=C

*.speclinguist-vendored=true

-PGVERSION=9.5 CHECK_CODE=false

script:bash ./travis/pg-travis-test.sh

after_success:

-bash <(curl -s https://codecov.io/bash)

MODULE_big = pg_pathman

OBJS = src/init.o src/relation_info.o src/utils.o src/partition_filter.o\

src/runtimeappend.o src/runtime_merge_append.o src/pg_pathman.o src/rangeset.o\

src/pl_funcs.o src/pl_range_funcs.o src/pl_hash_funcs.o src/pathman_workers.o\

src/hooks.o src/nodes_common.o src/xact_handling.o src/utility_stmt_hooking.o\

src/planner_tree_modification.o src/debug_print.o src/pg_compat.o\

src/partition_creation.o$(WIN32RES)

src/planner_tree_modification.o src/debug_print.o src/partition_creation.o\

src/compat/pg_compat.o$(WIN32RES)

PG_CPPFLAGS = -I$(CURDIR)/src/include

EXTENSION = pg_pathman

EXTVERSION = 1.2

EXTVERSION = 1.3

DATA_built = pg_pathman--$(EXTVERSION).sql

DATA = pg_pathman--1.0.sql\

pg_pathman--1.0--1.1.sql\

pg_pathman--1.1.sql\

pg_pathman--1.1--1.2.sql

DATA = pg_pathman--1.0--1.1.sql\

pg_pathman--1.1--1.2.sql\

pg_pathman--1.2--1.3.sql

PGFILEDESC = "pg_pathman - partitioning tool"

REGRESS = pathman_basic\

pathman_cte\

pathman_bgw\

pathman_inserts\

pathman_runtime_nodes\

pathman_callbacks\

pathman_updates\

pathman_domains\

pathman_interval\

pathman_callbacks\

pathman_foreign_keys\

pathman_permissions\

pathman_rowmarks\

pathman_runtime_nodes\

pathman_utility_stmt_hooking\

pathman_calamity

EXTRA_REGRESS_OPTS=--temp-config=$(top_srcdir)/$(subdir)/conf.add

EXTRA_CLEAN = pg_pathman--$(EXTVERSION).sql ./isolation_output

[](https://travis-ci.org/postgrespro/pg_pathman)

[](https://badge.fury.io/pg/pg_pathman)

[](https://codecov.io/gh/postgrespro/pg_pathman)

In order to update pg_pathman:

1. Install the latest_stable_ release of pg_pathman.

2. Restart your PostgreSQL cluster.

3. Execute the following queries:

ALTER EXTENSION pg_pathmanUPDATE TO"X.Y";

SETpg_pathman.enable= t;

create_hash_partitions(relation REGCLASS,

attributeTEXT,

partitions_countINTEGER,

partition_dataBOOLEAN DEFAULT TRUE)

partition_dataBOOLEAN DEFAULT TRUE,

partition_namesTEXT[] DEFAULTNULL,

tablespacesTEXT[] DEFAULTNULL)

Performs HASH partitioning for`relation` by integer key`attribute`. The`partitions_count` parameter specifies the number of partitions to create; it cannot be changed afterwards. If`partition_data` is`true` then all the data will be automatically copied from the parent table to partitions. Note that data migration may took a while to finish and the table will be locked until transaction commits. See`partition_table_concurrently()` for a lock-free way to migrate data. Partition creation callback is invoked for each partition if set beforehand (see`set_init_callback()`).

p_countINTEGER DEFAULTNULL,

partition_dataBOOLEAN DEFAULT TRUE)

Performs RANGE partitioning for`relation` by partitioning key`attribute`.`start_value` argument specifies initial value,`interval` sets the rangeof values in a singlepartition,`count` is the number of premade partitions (if not set thenpathman tries to determine it based on attribute values). Partition creation callback is invoked for each partition if set beforehand.

Performs RANGE partitioning for`relation` by partitioning key`attribute`,`start_value` argument specifies initial value,`p_interval` sets thedefaultrangefor auto created partitions or partitions created with`append_range_partition()` or`prepend_range_partition()` (if`NULL` then autopartition creation feature won't work),`p_count` is the number of premade partitions (if not set then`pg_pathman` tries to determine it based on attribute values). Partition creation callback is invoked for each partition if set beforehand.

create_partitions_from_range(relation REGCLASS,

replace_hash_partition(old_partitionREGCLASS,

new_partitionREGCLASS,

lock_parentBOOL DEFAULT TRUE)

replace_hash_partition(old_partition REGCLASS,

new_partition REGCLASS,

lock_parent BOOL DEFAULT TRUE)

Replaces specified partition of HASH-partitioned table with another table. The`lock_parent` parameter will prevent any INSERT/UPDATE/ALTER TABLE queries to parent table.

Merge two adjacent RANGE partitions. First, data from`partition2` is copied to`partition1`, then`partition2` is removed.

merge_range_partitions(partitions REGCLASS[])

Merge several adjacent RANGE partitions (partitions must be specified in ascending or descending order). All the data will be accumulated in the first partition.

append_range_partition(parent REGCLASS,

partition_nameTEXT DEFAULTNULL,

partition_nameTEXT DEFAULTNULL,

tablespaceTEXT DEFAULTNULL)

Create new RANGE partition for`relation` with specified range bounds.

Create new RANGE partition for`relation` with specified range bounds. If`start_value` or`end_value` are NULL then corresponding range bound will be infinite.

drop_range_partition(partitionTEXT, delete_dataBOOLEAN DEFAULT TRUE)

set_interval(relation REGCLASS, value ANYELEMENT)

Update RANGE partitioned table interval. Note that interval must not be negative and it must not be trivial, i.e. its value should be greater than zero for numeric types, at least 1 microsecond for`TIMESTAMP` and at least 1 day for`DATE`.

set_enable_parent(relation REGCLASS, valueBOOLEAN)

{

"parent":"abc",

"parent_schema":"public",

"parttype":"2",

"partition":"abc_4",

"partition_schema":"public",

"range_max":"401",

"range_min":"301"

}

{

"parent":"abc",

"parent_schema":"public",

"parttype":"1",

"partition":"abc_0"

"partition_schema":"public"

}

Ildar Musin <i.musin@postgrespro.ru> Postgres Professional Ltd., Russia

Alexander Korotkov <a.korotkov@postgrespro.ru> Postgres Professional Ltd., Russia

Dmitry Ivanov <d.ivanov@postgrespro.ru> Postgres Professional Ltd., Russia