pg_plan_filter 1.0.0 released

What happened

The module could be extended to support further kinds of filters. This loadable module test sstatements against specific configured criteria before execution, raising an error if the criteria are violated.

This allows administrators to prevent execution of certain queries on production databases. The criteria are based on the planner's estimated cost.

pg_plan_filter can refuse an individual statement whose plan is too expensive ( statement_cost_limit ), cap the combined cost of all the statements run in one transaction ( transaction_cost_limit ), and optionally apply the filter to SELECT statements only ( filter_select_only ). It provides support for PostgreSQL versions 14 through 18.