From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: james.inform@pharmapp.de
Subject: BUG #17146: pg_dump statements are going into pg_stat_statements in 13.4
Date: Sun, 15 Aug 2021 17:30:52 +0000
Message-ID: <17146-fd449661169489e5@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 17146
Logged by: James Inform
Email address: james.inform@pharmapp.de
PostgreSQL version: 13.4
Operating system: Ubuntu 18.04 LTS AND macOS Catalina 10.15.7
Description:
Hi
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.
This is a new behaviour in 13.4 and hasn't existed in 13.3 and prior.
Is there a setting to prevent this?
Cheers,
James
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: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, james.inform@pharmapp.de
Subject: Re: BUG #17146: pg_dump statements are going into pg_stat_statements in 13.4
In-Reply-To: <17146-fd449661169489e5@postgresql.org>
* 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