BUG #17665: pg_stat_statements useless with variable number of parameters in IN close

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: bokanist(at)gmail(dot)com
Subject: BUG #17665: pg_stat_statements useless with variable number of parameters in IN close
Date: 2022-10-27 10:42:52
Message-ID: 17665-d10ccd445cd66f6c@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 17665
Logged by: Sebastien Caunes
Email address: bokanist(at)gmail(dot)com
PostgreSQL version: 15.0
Operating system: all
Description:

Not really a bug, but this issue makes pg_stat_statements almost useless.

One of my customer have queries with variables number of parameters in IN
closes

SELECT * FROM my_table WHERE id IN ($1, $2, $3, $4, ...) -- number of
parameters varies from one to thousands

And some queries have more than one IN close. This bloat the
pg_stat_statement table with all different version of the same query.

I think the parameters in IN close should be merged as one.
By the way, where should I submit this kind of improvement request ?

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2022-10-27 11:37:20 BUG #17666: Unexpected shutdown
Previous Message PG Bug reporting form 2022-10-26 09:00:58 BUG #17664: The subsctring() function with the char() text type does not work correctly