Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vJBUy-00Dg21-14 for pgsql-admin@arkaria.postgresql.org; Wed, 12 Nov 2025 14:06:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vJBUw-00Bnd7-0G for pgsql-admin@arkaria.postgresql.org; Wed, 12 Nov 2025 14:06:58 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vJBUv-00Bncz-2K for pgsql-admin@lists.postgresql.org; Wed, 12 Nov 2025 14:06:57 +0000 Received: from mail-oi1-x235.google.com ([2607:f8b0:4864:20::235]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vJBUt-007M3u-0P for pgsql-admin@lists.postgresql.org; Wed, 12 Nov 2025 14:06:57 +0000 Received: by mail-oi1-x235.google.com with SMTP id 5614622812f47-44ffed84cccso159980b6e.0 for ; Wed, 12 Nov 2025 06:06:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1762956413; x=1763561213; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=xe42MricqgduMYymrwO7OJMeGxsDYuN4BasItNUivKc=; b=QFadkcgi2DmXzC3KIqPdBkseSaAgIaInMuNqcxR3cwXVh2L3SlAkn2zElghKHai8Fk h89pYj2+KnJFvr5cxjnc7Mv5ANm4zLfHikY4oy+ZTCJQQwheHB466gGw67ttNPIzNmfd BkECYEmZf0VHiQYijI40z6CpFKNYx0Duk0G7GLq+Hp7OjvCC0o3SXTbhKTh36UnSkteO VaQDOJOswmSFw8gSPDWaddG8MzzC5gb994Ai1rV2xI+ZR/VXt9ohRqpO7iZ1zXx3A6Kf 1PGiHgE9E2EG3neHsms2/zOAEoz1vz+jI3TN7hcIFyrwMLbiZuqtjQhmKu9t4jA+vhwR T34w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1762956413; x=1763561213; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=xe42MricqgduMYymrwO7OJMeGxsDYuN4BasItNUivKc=; b=AyrqG41nzSO7U6Zksj2Mo4IVABRac7Nd5k9QLOpObP/1/Q9VIvQ3q9uNfNlwnCbLO3 IIczJzynKPqbkZTCG0/2OdjquWfKcRTob7wNLaZF9sf+2BTO/rbmE+yeOSkt6ArrBMQq gaGgvCR4BAJlPSBrXNjWBC5UeN+LmJNciSc12ERurYaBtiAV6PBsD8TMFRjbR/wVmTkB xD2AZQAZ/TdOX7zZsdfEuNyeAUix+d85yet3DuiCXU5+JNQNVStiE5ilHI0HiZDIn0vL rmZVowe43GQi8fibIOSssVC0WH4FvXoa4trM5RQn9KbgCsUOVVfsAS7fc+TyDoyXNkCJ e8bA== X-Gm-Message-State: AOJu0YzHEtze5zsgajz8pWY+mIN1MN2sls2ApamcDQjh5oM+s7z1zBf/ 6m74nL316cVISlrRmdujN4sw80iJLoiVcJNJUxd0HrF1BE874cC9MZNOU1/LaUdWD9lS3utsaU6 ep2KShMc8skf9M0mtZGUtMU1KWNd5wKQPFw== X-Gm-Gg: ASbGncvEfIsXzfp7+PPdcSO1Pio9+HZKbiV2z047QdClEUICe8cs/FAkw0OX8jwG3ag gMNdGBzDnb6x2XjI3cepp3/+Y0y9WNfm8SQLpWsmH2ZaHim1FJWOngz/NsbXwkp9frxiaP+qw6F wpnA3uFhCrxnveWpawK4bXYXvGzYT98nDLvj/8IevaWYUT1ujkpBXBtAQ8oj4LSNrG9z7/pDRPu rFlOJC0/i+jzdVNdIzp2UU4BIZCGNNqUYSHl5aKF5aWPPrVxBOwCKaBRa+a3SppPpq7/2QF X-Google-Smtp-Source: AGHT+IGZht45a3Gj/wgHHWN6AUpWa8XgrBy9iOSeXWTVYoHHubykRWE+aXWSjw/JlBmHe40d8wOkc3SWOB4k8f4JSRc= X-Received: by 2002:a05:6808:c148:b0:442:e596:1189 with SMTP id 5614622812f47-450745e3d06mr1442687b6e.45.1762956413025; Wed, 12 Nov 2025 06:06:53 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Wed, 12 Nov 2025 09:06:41 -0500 X-Gm-Features: AWmQ_blTCz_9IgRtvr1pGM9f5BgprLMTqaS_FN2d1AnXm-BB2H6WyHhYiVBbpyM Message-ID: Subject: Re: Monitoring PostgreSQL Copy Operations To: Pgsql-admin Content-Type: multipart/alternative; boundary="000000000000c0c0c70643664680" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000c0c0c70643664680 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Nov 12, 2025 at 3:33=E2=80=AFAM Abdullah Ergin wrote: > To monitor Copy operations in PostgreSQL in real-time, I use the =E2=80= =9C > pg_stat_progress_copy > =E2=80=9D > view tool: > > Here, I specifically want to analyze the number of tuples processed by th= e > command, which is =E2=80=9Ctuples_processed=E2=80=9D. However, since pg_s= tat_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" --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --000000000000c0c0c70643664680 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Nov 12, 2025 at 3:33=E2=80=AFAM A= bdullah Ergin <abdullaher= ginwork@gmail.com> wrote:

To monitor Copy operations in = PostgreSQL in real-time, I use the =E2=80=9Cpg_stat_progress_copy=E2= =80=9D view tool:

Here, I speci= fically want to analyze the number of tuples processed by the command, whic= h is =E2=80=9Ctuples_processed=E2=80=9D. However, since pg_stat_progress_co= py is a view tool, the information disappears once the operation is complet= e, and it does not save the result of the copy operation anywhere. How can = I save the result of the copy operation?

Pip= e the query output=C2=A0to "tee -a blarge.log"=C2=A0
--
Death to <Redacted&g= t;, and butter sauce.
Don't boil me, I'm still alive.
<= div><Redacted> lobster!
--000000000000c0c0c70643664680--