From: hubert depesz lubaczewski <depesz@depesz.com>
To: james.inform@pharmapp.de
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17146: pg_dump statements are going into pg_stat_statements in 13.4
Date: Mon, 16 Aug 2021 11:23:45 +0200
Message-ID: <20210816092345.GA8258@depesz.com> (raw)
In-Reply-To: <17146-fd449661169489e5@postgresql.org>
References: <17146-fd449661169489e5@postgresql.org>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: depesz@depesz.com, 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
In-Reply-To: <20210816092345.GA8258@depesz.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox