A prepared statement in PostgreSQL has switched to a generic plan. The DBA wants to force per-execution custom plans for this session because of parameter skew. Which mechanism actually controls this decision, and what is its non-obvious caveat?
SET plan_cache_mode = 'force_custom_plan';