EXPLAIN (GENERIC_PLAN) Fails With Bind Message Error on Postgres 17.2
Despite running PostgreSQL 17.2 across local, vanilla Ubuntu, and AWS RDS instances, a reader reports that EXPLAIN (GENERIC_PLAN) fails when applied to parameterized queries sourced from pg_stat_statements. The attempt triggers a SQL error: ERROR: bind message supplies 0 parameters, but prepared statement "" requires 1.
No extension installation or GUC changes appear necessary per official documentation, and PostgreSQL 17 docs list GENERIC_PLAN among valid EXPLAIN options. Still, the feature refuses to execute on a 17.2 database.
The question remains: why would GENERIC_PLAN not function on version 17.2, and is there a workaround for analyzing such statements?
