Re: [PATCH] Simple progress reporting for COPY command - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: [PATCH] Simple progress reporting for COPY command
Date
Msg-id CAA4eK1+wYBP0kE60jX5knn0bXyuZjp7kcNRSBCSK7gkLbikdAg@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Simple progress reporting for COPY command  (Josef Šimánek <josef.simanek@gmail.com>)
Responses Re: [PATCH] Simple progress reporting for COPY command
List pgsql-hackers
On Fri, Jan 8, 2021 at 8:42 AM Josef Šimánek <josef.simanek@gmail.com> wrote:
>
> pá 8. 1. 2021 v 3:55 odesílatel Amit Kapila <amit.kapila16@gmail.com> napsal:
> >
> >
> > Can't we display the entire COPY command? I checked that
> > pg_stat_statements display the query so there shouldn't be a problem
> > to display the entire command.
>
> In previous discussions there was mentioned it doesn't make sense
> since you can join with pg_stat_statements on the pid column if
> needed. What would be the reason to duplicate that info?
>

But pg_stat_staments won't be present by default. Also, the same
argument could be applied for the command to be present in
stat_progress views. It occurred to me only when I was trying to
compare what we display in all the progress views. I think there is
some merit in being consistent.

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Keisuke Kuroda
Date:
Subject: Re: Huge memory consumption on partitioned table with FKs
Next
From: Josef Šimánek
Date:
Subject: Re: [PATCH] Simple progress reporting for COPY command