pá 8. 1. 2021 v 3:55 odesílatel Amit Kapila <amit.kapil...@gmail.com> napsal: > > On Thu, Jan 7, 2021 at 7:02 PM Josef Šimánek <josef.sima...@gmail.com> wrote: > > > > čt 7. 1. 2021 v 14:08 odesílatel Amit Kapila <amit.kapil...@gmail.com> > > napsal: > > > > > > On Thu, Jan 7, 2021 at 3:15 AM Tomas Vondra > > > <tomas.von...@enterprisedb.com> wrote: > > > > > > > > On 1/5/21 11:02 AM, Josef Šimánek wrote: > > > > > I'm attaching the whole patch since commitfest failed to ingest the > > > > > last incremental on CI. > > > > > > > > > > > > > Yeah, the whole patch needs to be attached for the commitfest tester to > > > > work correctly - it can't apply pieces from multiple messages, etc. > > > > > > > > Anyway, I pushed this last version of patch, after a couple more tweaks, > > > > mainly to the docs - one place used pg_stat_copy_progress, the section > > > > was not indexed properly, and so on. > > > > > > > > > > How about including a column for command similar to > > > pg_stat_progress_create_index and pg_stat_progress_cluster? It seems > > > that command will be useful in the context of COPY as there are many > > > variants of COPY. > > > > > > > From pg_stat_progress_create_index docs: > > > > The command that is running: CREATE INDEX, CREATE INDEX CONCURRENTLY, > > REINDEX, or REINDEX CONCURRENTLY. > > > > Which values should be present in copy progress? Just COPY FROM or COPY TO? > > > > 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? > -- > With Regards, > Amit Kapila.
