Re: [PATCH] Initial progress reporting for COPY command

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: Josef Šimánek <josef(dot)simanek(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Subject: Re: [PATCH] Initial progress reporting for COPY command
Date: 2020-06-15 04:38:57
Message-ID: 9d0d0fcb-b9bb-584e-3151-0d45c868a684@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

> 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?

Regards,

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2020-06-15 04:42:25 Re: Review for GetWALAvailability()
Previous Message Masahiko Sawada 2020-06-15 04:30:58 Re: vacuum verbose: show pages marked allvisible/frozen/hintbits