Re: BUG #17146: pg_dump statements are going into pg_stat_statements in 13.4

On Mon, Aug 16, 2021 at 4:46 PM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
>
> The following bug has been logged on the website:
>
> I have just updated to 13.4 and I have noticed that "COPY" statements that
> are produced by pg_dump appear in pg_stat_statements view.
>
> You can imagine that the copy statements are slower than all my other
> statements, so they come up as the first and most expensive statements in
> pg_stat_statements.

You could order by the average execution time rather than the total
execution time and/or filter out queries executed less than X times,
it's more likely to give you low hanging fruits.

> This is a new behaviour in 13.4 and hasn't existed in 13.3 and prior.

Nothing changed here for a long time.

> Is there a setting to prevent this?

You could disable pg_stat_statements.track_utility, but it obviously
means that all utility statements will be ignored, not only COPY.