public inbox for [email protected]  

help / color / mirror / Atom feed

From: Ron Johnson <[email protected]>
To: Pgsql-admin <[email protected]>
Subject: Re: Monitoring PostgreSQL Copy Operations
Date: Wed, 12 Nov 2025 09:06:41 -0500
Message-ID: <CANzqJaDOimOC7cTP7zwt3BjR8stQ+fj-iz+crrAow=c+m4QXkw@mail.gmail.com> (raw)
In-Reply-To: <CAJZxWEOP7TwFcd1WrKRTL9XxXmxLKKzft5d_XYs_diLo+Uc-Nw@mail.gmail.com>
References: <CAJZxWEOP7TwFcd1WrKRTL9XxXmxLKKzft5d_XYs_diLo+Uc-Nw@mail.gmail.com>

On Wed, Nov 12, 2025 at 3:33 AM Abdullah Ergin <[email protected]>
wrote:

> To monitor Copy operations in PostgreSQL in real-time, I use the “
> pg_stat_progress_copy
> <https://www.postgresql.org/docs/current/progress-reporting.html#COPY-PROGRESS-REPORTING>”
> view tool:
>
> Here, I specifically want to analyze the number of tuples processed by the
> command, which is “tuples_processed”. However, since pg_stat_progress_copy
> is a view tool, the information disappears once the operation is complete,
> and it does not save the result of the copy operation anywhere. How can I
> save the result of the copy operation?
>
Pipe the query output to "tee -a blarge.log"

-- 
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

view thread (2+ messages)

reply

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: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Monitoring PostgreSQL Copy Operations
  In-Reply-To: <CANzqJaDOimOC7cTP7zwt3BjR8stQ+fj-iz+crrAow=c+m4QXkw@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox