[*]

indent_style =tab

indent_size =4

-gcc

before_install:

-sudo sh ./travis/apt.postgresql.org.sh

-if [[ "$TRAVIS_OS_NAME" == "linux" ]]; then sudo apt-get -y install -qq wget ca-certificates; fi

-if [[ "$TRAVIS_OS_NAME" == "linux" ]]; then source ./travis/dep-ubuntu-postgres.sh; fi

-if [[ "$TRAVIS_OS_NAME" == "linux" ]]; then source ./travis/dep-ubuntu-llvm.sh; fi

-if [[ "$TRAVIS_OS_NAME" == "linux" ]]; then sudo apt-get update -qq; fi

env:

-PGVERSION=9.6 CHECK_CODE=true

-PGVERSION=9.6 CHECK_CODE=false

-PGVERSION=9.5 CHECK_CODE=true

-PGVERSION=9.5 CHECK_CODE=false

global:

-LLVM_VER=4.0

matrix:

-PG_VER=10 CHECK_CODE=true

-PG_VER=10 CHECK_CODE=false

-PG_VER=9.6 CHECK_CODE=true

-PG_VER=9.6 CHECK_CODE=false

-PG_VER=9.5 CHECK_CODE=true

-PG_VER=9.5 CHECK_CODE=false

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

"name":"pg_pathman",

"abstract":"Partitioning tool",

"description":"The `pg_pathman` module provides optimized partitioning mechanism and functions to manage partitions.",

"version":"1.3.1",

"version":"1.4.2",

"maintainer": [

"Ildar Musin <i.musin@postgrespro.ru>",

"Dmitry Ivanov <d.ivanov@postgrespro.ru>",

"generated_by":"Ildar Musin",

"provides": {

"pg_pathman": {

"file":"pg_pathman--1.3.sql",

"file":"pg_pathman--1.4.sql",

"docfile":"README.md",

"version":"1.3.1",

"version":"1.4.2",

"abstract":"Partitioning tool"

}

},

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 src/compat/relation_tags.o src/compat/rowmarks_fix.o\

overridePG_CPPFLAGS += -I$(CURDIR)/src/include

EXTENSION = pg_pathman

EXTVERSION = 1.3

EXTVERSION = 1.4

DATA_built = pg_pathman--$(EXTVERSION).sql

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

pg_pathman--1.1--1.2.sql\

pg_pathman--1.2--1.3.sql

pg_pathman--1.2--1.3.sql\

pg_pathman--1.3--1.4.sql

PGFILEDESC = "pg_pathman - partitioning tool"

PGFILEDESC = "pg_pathman - partitioning tool for PostgreSQL"

REGRESS =pathman_basic\

REGRESS =pathman_array_qual\

pathman_bgw\

pathman_inserts\

pathman_updates\

pathman_domains\

pathman_interval\

pathman_calamity\

pathman_callbacks\

pathman_column_type\

pathman_cte\

pathman_domains\

pathman_expressions\

pathman_foreign_keys\

pathman_inserts\

pathman_interval\

pathman_join_clause\

pathman_lateral\

pathman_mergejoin\

pathman_only\

pathman_param_upd_del\

pathman_permissions\

pathman_rebuild_updates\

pathman_rowmarks\

pathman_runtime_nodes\

pathman_utility_stmt_hooking\

pathman_calamity\

pathman_join_clause

pathman_update_trigger\

pathman_utility_stmt

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

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

--outputdir=./isolation_output\

python_tests:

$(MAKE) -C tests/python partitioning_tests

cmocka_tests:

$(MAKE) -C tests/cmocka check

The`pg_pathman` module provides optimized partitioning mechanism and functions to manage partitions.

The extension is compatible with PostgreSQL 9.5+.

The extension is compatible with:

* PostgreSQL 9.5, 9.6, 10;

* Postgres Pro Standard 9.5, 9.6;

* Postgres Pro Enterprise;

By the way, we have a growing Wiki[out there](https://github.com/postgrespro/pg_pathman/wiki).

**Partitioning** means splitting one large table into smaller pieces. Each row in such table is moved to a single partition according to the partitioning key. PostgreSQL supports partitioning via table inheritance: each partition must be created as a child table with CHECK CONSTRAINT. For example:

* HASH and RANGE partitioning schemes;

* Partitioning by expression and composite key;

* Both automatic and manual partition management;

* Support for integer, floating point, date and other types, including domains;

* Effective query planning for partitioned tables (JOINs, subselects etc);

* Various GUC toggles and configurable settings.

* Multi-level partitioning (ver 1.5);

* Improved referential integrity + foreign keys on partitioned tables (ver 1.5);

* Implement LIST partitioning scheme;

* Optimize hash join (both tables are partitioned by join key).

Take a look at[this page](https://github.com/postgrespro/pg_pathman/wiki/Roadmap);

To install`pg_pathman`, execute this in the module's directory:

create_hash_partitions(relation REGCLASS,

attributeTEXT,

exprTEXT,

partitions_countINTEGER,

partition_dataBOOLEAN DEFAULT TRUE,

partition_namesTEXT[] DEFAULTNULL,

tablespacesTEXT[] DEFAULTNULL)

Performs HASH partitioning for`relation` byinteger 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()`).

Performs HASH partitioning for`relation` bypartitioning expression`expr`. 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()`).

create_range_partitions(relation REGCLASS,

attributeTEXT,

start_value ANYELEMENT,

p_interval ANYELEMENT,

p_countINTEGER DEFAULTNULL

partition_dataBOOLEAN DEFAULT TRUE)

create_range_partitions(relation REGCLASS,

expressionTEXT,

start_value ANYELEMENT,

p_interval ANYELEMENT,

p_countINTEGER DEFAULTNULL

partition_dataBOOLEAN DEFAULT TRUE)

create_range_partitions(relation REGCLASS,

expressionTEXT,

start_value ANYELEMENT,

p_interval INTERVAL,

p_countINTEGER DEFAULTNULL,

partition_dataBOOLEAN DEFAULT TRUE)

create_range_partitions(relation REGCLASS,

attributeTEXT,

start_valueANYELEMENT,

p_interval INTERVAL,

p_countINTEGER DEFAULTNULL,

partition_dataBOOLEAN DEFAULT TRUE)

create_range_partitions(relationREGCLASS,

expressionTEXT,

bounds ANYARRAY,

partition_namesTEXT[] DEFAULTNULL,

tablespacesTEXT[] DEFAULTNULL,

partition_dataBOOLEAN DEFAULT TRUE)

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

Performs RANGE partitioning for`relation` by partitioningexpression`expr`,`start_value` argument specifies initial value,`p_interval` sets the default range for auto created partitions or partitions created with`append_range_partition()` or`prepend_range_partition()` (if`NULL` then auto partition creation feature won't work),`p_count` is the number of premade partitions (if not set then`pg_pathman` tries to determine it based onexpression's values). The`bounds` array can be built using`generate_range_bounds()`. Partition creation callback is invoked for each partition if set beforehand.

create_partitions_from_range(relation REGCLASS,

attributeTEXT,

start_value ANYELEMENT,

end_value ANYELEMENT,

p_interval ANYELEMENT,

partition_dataBOOLEAN DEFAULT TRUE)

generate_range_bounds(p_start ANYELEMENT,

p_interval INTERVAL,

p_countINTEGER)

create_partitions_from_range(relation REGCLASS,

attributeTEXT,

start_value ANYELEMENT,

end_value ANYELEMENT,

p_interval INTERVAL,

partition_dataBOOLEAN DEFAULT TRUE)

generate_range_bounds(p_start ANYELEMENT,

p_interval ANYELEMENT,

p_countINTEGER)

Performs RANGE-partitioning from specified range for`relation` by partitioning key`attribute`. Partition creation callback is invoked for each partition if set beforehand.

Builds`bounds` array for`create_range_partitions()`.

create_hash_update_trigger(parent REGCLASS)

Creates the trigger on UPDATE for HASH partitions. The UPDATE trigger isn't created by default because of the overhead. It's useful in cases when thekey attribute might change.

Creates the trigger on UPDATE for HASH partitions. The UPDATE trigger isn't created by default because of the overhead. It's useful in cases when thepartitioning expression's value might change.

create_range_update_trigger(parent REGCLASS)

{

"parent":"abc",

"parttype":"2",

"partition":"abc_4",

"range_max":"401",

"range_min":"301"

"parent":"abc",

"parent_schema":"public",

"parttype":"2",

"partition":"abc_4",

"partition_schema":"public",

"range_max":"401",

"range_min":"301"

}

{

"parent":"abc",

"parttype":"1",

"partition":"abc_0"

"parent":"abc",

"parent_schema":"public",

"parttype":"1",

"partition":"abc_0",

"partition_schema":"public"

}

CREATETABLEIF NOT EXISTS pathman_config (

partrel REGCLASSNOT NULLPRIMARY KEY,

attnameTEXTNOT NULL,

exprTEXTNOT NULL,

parttypeINTEGERNOT NULL,

range_intervalTEXT);

range_intervalTEXT,

cooked_exprTEXT);

This table stores a list of partitioned tables.

enable_parentBOOLEANNOT NULL DEFAULT TRUE,

autoBOOLEANNOT NULL DEFAULT TRUE,

init_callback REGPROCEDURENOT NULL DEFAULT0,

spawn_using_bgwBOOLEANNOT NULL DEFAULT FALSE);

spawn_using_bgwBOOLEANNOT NULL DEFAULT FALSE);

This table stores optional parameters which override standard behavior.

parent REGCLASS,

partition REGCLASS,

parttype INT4,

partattrTEXT,

exprTEXT,

range_minTEXT,

range_maxTEXT)

AS'pg_pathman','show_partition_list_internal'

This view lists all existing partitions, as well as their parents and range boundaries (NULL for HASH partitions).

CREATEOR REPLACE FUNCTION @extschema@.show_cache_stats()

RETURNS TABLE (

contextTEXT,

size INT8,

used INT8,

entries INT8)

AS'pg_pathman','show_cache_stats_internal'

LANGUAGE C STRICT;

CREATEOR REPLACE VIEW @extschema@.pathman_cache_stats

ASSELECT*FROM @extschema@.show_cache_stats();

Shows memory consumption of various caches.

`pg_pathman` provides a couple of[custom plan nodes](https://wiki.postgresql.org/wiki/CustomScanAPI) which aim to reduce execution time, namely:

-`pg_pathman.enable_runtimemergeappend` --- toggle`RuntimeMergeAppend` custom node on\off

-`pg_pathman.enable_partitionfilter` --- toggle`PartitionFilter` custom node on\off

-`pg_pathman.enable_auto_partition` --- toggle automatic partition creation on\off (per session)

-`pg_pathman.enable_bounds_cache` --- toggle bounds cache on\off (faster updates of partitioning scheme)

-`pg_pathman.insert_into_fdw` --- allow INSERTs into various FDWs`(disabled | postgres | any_fdw)`

-`pg_pathman.override_copy` --- toggle COPY statement hooking on\off

Do not hesitate to post your issues, questions and new ideas at the[issues](https://github.com/postgrespro/pg_pathman/issues) page.

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

Ildar Musin <i.musin(at)postgrespro.ru> Postgres Professional Ltd., Russia

Alexander Korotkov <a.korotkov(at)postgrespro.ru> Postgres Professional Ltd., Russia

Dmitry Ivanov <d.ivanov(at)postgrespro.ru> Postgres Professional Ltd., Russia

Maksim Milyutin <m.milyutin(at)postgrespro.ru> Postgres Professional Ltd., Russia

Ildus Kurbangaliev <i.kurbangaliev(at)postgrespro.ru> Postgres Professional Ltd., Russia