Postgres Pro
Downloads
Home   >   mailing lists

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

From Josef Šimánek
Subject Re: [PATCH] Initial progress reporting for COPY command
Date
Msg-id CAFp7QwoN=PMbTC2xJMUfZ=7EJ_bm=8biG1ag+Bwu6m6AT9g51A@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Initial progress reporting for COPY command  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Responses Re: [PATCH] Initial progress reporting for COPY command
List pgsql-hackers
Tree view


po 15. 6. 2020 v 6:39 odesílatel Fujii Masao <masao.fujii@oss.nttdata.com> napsal:


On 2020/06/14 21:32, Josef Šimánek wrote:
> Hello, as proposed by Pavel Stěhule and discussed on local czech PostgreSQL maillist (https://groups.google.com/d/msgid/postgresql-cz/CAFj8pRCZ42CBCa1bPHr7htffSV%2BNAcgcHHG0dVqOog4bsu2LFw%40mail.gmail.com?utm_medium=email&utm_source=footer), I have prepared an initial patch for COPY command progress reporting.

Sounds nice!


> file - bool - is file is used?
> program - bool - is program used?

Are these fields really necessary in a progress view?
What values are reported when STDOUT/STDIN is specified in COPY command?

For STDOUT and STDIN file is true and program is false.
 
> file_bytes_processed - amount of bytes processed when file is used (otherwise 0), works for both direction (
> FROM/TO) when file is used (file = t)

What value is reported when STDOUT/STDIN is specified in COPY command?

For my first patch nothing was reported on STDOUT/STDIN usage. I'll attach new patch soon supporting those as well.
 
 
 
Regards,


--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

pgsql-hackers by date:

Previous
From: Josef Šimánek
Date:
Subject: Re: [PATCH] Initial progress reporting for COPY command
Next
From: Josef Šimánek
Date:
Subject: Re: [PATCH] Initial progress reporting for COPY command