Re: [PATCH] Initial progress reporting for COPY command
vignesh C <vignesh21@gmail.com>
From: vignesh C <vignesh21@gmail.com>
To: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: Josef Šimánek <josef.simanek@gmail.com>, Pg Hackers <pgsql-hackers@postgresql.org>, Pavel Stehule <pavel.stehule@gmail.com>
Date: 2020-06-25T01:05:22Z
Lists: pgsql-hackers
On Tue, Jun 23, 2020 at 4:45 PM Tomas Vondra <tomas.vondra@2ndquadrant.com> wrote: > > >> > >> Anyway if you would like to make this view more user-friendly, I can add that. Just ping me. > > > >I felt we could add pg_size_pretty to make the view more user friendly. > > > > Please no. That'd make processing of the data (say, computing progress > as processed/total) impossible. It's easy to add pg_size_pretty if you > want it, it's impossible to undo it. I don't see a single pg_size_pretty > call in system_views.sql. > I thought of including pg_size_pretty as we there was no total_bytes to compare with, but I'm ok without it too as there is an option for user to always include it in the client side like "SELECT pg_size_pretty(file_bytes_processed) from pg_stat_progress_copy;" if required. Regards, Vignesh EnterpriseDB: http://www.enterprisedb.com
Commits
-
Report progress of COPY commands
- 8a4f618e7ae3 14.0 landed
-
Doc fixup for hashagg_avoid_disk_plan GUC.
- 7ce461560159 14.0 cited
-
Fix inconsistent markups in catalogs.sgml
- fe186b4c200b 14.0 cited