| From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Monitoring PostgreSQL Copy Operations |
| Date: | 2025-11-12 14:06:41 |
| Message-ID: | CANzqJaDOimOC7cTP7zwt3BjR8stQ+fj-iz+crrAow=c+m4QXkw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, Nov 12, 2025 at 3:33 AM Abdullah Ergin <abdullaherginwork(at)gmail(dot)com>
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!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sam Stearns | 2025-11-12 15:12:16 | Re: Re: Postgres Parameters |
| Previous Message | Abdullah Ergin | 2025-11-12 08:33:15 | Monitoring PostgreSQL Copy Operations |