Re: COPY table FROM STDIN doesn't show count tag

From: Rajeev rastogi <rajeev(dot)rastogi(at)huawei(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Amit Khandekar <amit(dot)khandekar(at)enterprisedb(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: COPY table FROM STDIN doesn't show count tag
Date: 2014-03-12 03:44:09
Message-ID: BF2827DCCE55594C8D7A8F7FFD3AB7713DDD7D45@SZXEML508-MBX.china.huawei.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11 March 2014 19:52, Tom Lane wrote:

> After sleeping on it, I'm inclined to think we should continue to not
> print status for COPY TO STDOUT. Aside from the risk of breaking
> scripts, there's a decent analogy to be made to SELECT: we don't print
> a status tag for that either.

It is correct that SELECT does not print conventional way of status tag but still it prints the number
of rows selected (e.g. (2 rows)) along with rows actual value, which can be very well considered
as kind of status. User can make out with this result, that how many rows have been selected.

But in-case of COPY TO STDOUT, if we don't print anything, then user does not have any direct way of finding
that how many rows were copied from table to STDOUT, which might have been very useful.

Please let me know your opinion or if I have missed something.

Thanks and Regards,
Kumar Rajeev Rastogi

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jaime Casanova 2014-03-12 03:50:28 Re: db_user_namespace a "temporary measure"
Previous Message Aidan Van Dyk 2014-03-12 03:20:12 Re: db_user_namespace a "temporary measure"