Releases: postgrespro/pg_pathman
Releases · postgrespro/pg_pathman
Version 1.2.1
Minor fixes and improvements:
- Fixed function
choose_range_partition_name()
for 32-bit platforms; - Removed BOM marks (caused broken builds on old compilers).
Version 1.2
- Parallel SeqScan support;
- Re-implemented some of
plpgsql
functions in C; - Implemented auto check constraints renaming for partitions;
- Added
replace_hash_partition()
function; SpawnPartitionsWorker
is disabled by default (can be enabled withset_spawn_using_bgw()
function);- Improved planning process (fixed bugs with inlined SQL functions, stability fixes);
- Auto created partitions share the same owner. (parent table owner);
- Partition creation now requires
INSERT
permission on parent table.
Version 1.1.1
- Fixed not working
attach_range_partition()
andadd_range_partition()
when relation is marked as 'partitioned' (viapathman_config
) but has no children; - Prevent
pathman_process_utility_hook()
from messing with other extensions, e.g.pg_stat_statements
(issue #42); - Enable partition creation for
COPY FROM
statement (can be switched off); - Minor improvements and stability fixes.
Version 1.1
New features and enhancements:
- PostgreSQL 9.6 support;
- Tablespace support (#11);
COPY FROM/TO
support for partitioned tables (only for UNIX-like systems);- Improved FDW support (redirect inserted rows);
- User-defined callbacks on partition creation events (#22);
- Permissions improvements (owner can manage his partitions without being superuser);
- Fixed
SELECT FOR SHARE / FOR UPDATE
handling; - Fixed
SELECT ... WHERE partitioned_attribute IN (...)
for RANGE partitioning; - Fixed unique inner & outer nested loop plan generation (sometimes there would be unwanted extra rows);
- Improved pl/PgSQL API (stability & performance, #39);
- Improved RANGE partitioning for domains and some other types.
Version 1.0.1
Fix wrong check constraint naming (function build_check_constraint_name_internal()
).
Release candidate #1
This release contains various bugfixes and improvements, such as reworked partitioning info cache, concurrent partitioning and PartitionFilter custom node (drop-in replacement for INSERT triggers).
Early prototype
The prototype features RuntimeAppend & RuntimeMergeAppend custom nodes capable of discarding useless partition scans dynamically at runtime. This version is now deprecated.