Date: Mon, 16 Aug 2021 11:23:45 +0200
From: hubert depesz lubaczewski <depesz@depesz.com>
Sender: depesz@depesz.com
To: james.inform@pharmapp.de, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17146: pg_dump statements are going into pg_stat_statements
 in 13.4
Message-ID: <20210816092345.GA8258@depesz.com>
Reply-To: depesz@depesz.com
References: <17146-fd449661169489e5@postgresql.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <17146-fd449661169489e5@postgresql.org>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: 
 <https://www.postgresql.org/message-id/20210816092345.GA8258%40depesz.com>
Precedence: bulk

On Sun, Aug 15, 2021 at 05:30:52PM +0000, PG Bug reporting form wrote:
> 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.

Of course they do. These are statements.

> 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.
> This is a new behaviour in 13.4 and hasn't existed in 13.3 and prior.

No, it's not.

I just tested to be 100% sure, on 12.6 and pg_dump queries are in
pg_stat_statements.

Just consider what would you do if excessive dumping was causing
problems. You want these to be gone from stats?

If you don't care about COPY, then filter it out using WHERE clause.

Best regards,

depesz