Keith Fiske
Keith Fiske
Currently excluding (see https://github.com/keithf4/pg_bloat_check/pull/6).
Don't think this column is needed in `part_config`, just the `sub_default_table` entry in `part_config_sub` to tell sub-partition parents what to do. Making an issue instead of dropping in 5.1 because...
See CHANGELOG for what is new and pending unit testing NOTE: THERE WILL BE NO UPGRADE PATH FROM THE BETA TO 5.1.0! Please only install on testing/dev systems. To install...
Check and see if the REPLICA IDENTITY property is inherited by native partitioning. If not, add this as a template feature.
See about setting `superuser = false` in `pg_partman.control` to allow non-superuser installation. With trigger-based partitioning going away, the last function that had SECURITY DEFINER left should be able to have...
The reapply_indexes.py script does not work properly with PG11. It only looks at the template table to see which indexes should be dropped/created on the children. Since most indexes don't...
Add some conditional code to the maintenance function so that it can be called manually on any node in a replication cluster (primary or standby) and run without throwing errors...
MAINTAINER NOTE: Creating a new issue to discuss/track this I am still extending my partitioning process and I found a new issue more or less related to this ticket. When...
Create a procedure that, given a table name, will drop all of its indexes. Use this procedure during retention maintenance and also document its usefulness outside of pg_partman.
PostgreSQL still does not have a means to automatically analyze a partition set from the parent level. Distinct statistics are gathered when this is done for optimized partition querying. Currently...