{
   "name": "pg_table_range",
   "abstract": "Planning-time partition pruning by per-partition data ranges, including non-key columns",
   "description": "pg_table_range prunes partitions at planning time from a compact per-partition summary of each column's actual data: its min/max range for btree-comparable scalar types, or a covering extent for range types and PostGIS geometry. Unlike native PostgreSQL partition pruning, it works on columns that are not the partition key. Summaries are stored in the index's own metapage and maintained incrementally on insert (like BRIN), so no REINDEX is needed, and pruning is conservative so results are always identical to running without it.",
   "version": "0.1.1",
   "maintainer": [
      "David Bitner <bitner@dbspatial.com>"
   ],
   "license": "mit",
   "provides": {
      "pg_table_range": {
         "abstract": "Planning-time partition pruning by per-partition data ranges, including non-key columns",
         "file": "pg_table_range.control",
         "docfile": "README.md",
         "version": "0.1.1"
      }
   },
   "prereqs": {
      "runtime": {
         "requires": {
            "PostgreSQL": "16.0.0"
         }
      }
   },
   "resources": {
      "homepage": "https://github.com/bitner/pg_table_range",
      "bugtracker": {
         "web": "https://github.com/bitner/pg_table_range/issues"
      },
      "repository": {
         "url": "git://github.com/bitner/pg_table_range.git",
         "web": "https://github.com/bitner/pg_table_range",
         "type": "git"
      }
   },
   "generated_by": "David Bitner",
   "meta-spec": {
      "version": "1.0.0",
      "url": "https://pgxn.org/meta/spec.txt"
   },
   "tags": [
      "partitioning",
      "partition pruning",
      "performance",
      "planner",
      "brin",
      "postgis",
      "index access method"
   ],
   "release_status": "stable"
}