review: psql command copy count tag

As mentioned by Pavel also, this patch will be very useful, which provides below enhancement:

1. Brings consistency between copy from “stdin” and “file”.

2. Consistent with server side copy statement.

3. Also fixes the issue related to “\copy destination file becomes default destination file for next command given in sequence”.

This has been in “Ready for committer” stage for long time.
Please check if this can be committed now or any other changes required.

Thanks and Regards,
Kumar Rajeev Rastogi
------------------------------------------------------------------------------------------------------------------------------
This e-mail and its attachments contain confidential information from HUAWEI, which
is intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!

From: Pavel Stehule [mailto:pavel.stehule@gmail.com]
Sent: 30 January 2014 01:57
To: PostgreSQL Hackers
Cc: Amit Khandekar; Rajeev rastogi
Subject: review: psql command copy count tag

related to /messages/by-id/BF2827DCCE55594C8D7A8F7FFD3AB7713DDB15F8@SZXEML508-MBX.china.huawei.com
Hello
1. I had to rebase this patch - actualised version is attached - I merged two patches to one
2. The psql code is compiled without issues after patching
3. All regress tests are passed without errors
5. We like this feature - it shows interesting info without any slowdown - psql copy command is more consistent with server side copy statement from psql perspective.
This patch is ready for commit
Regards

Pavel

Rajeev rastogi <rajeev.rastogi@huawei.com> writes:

This has been in “Ready for committer” stage for long time.

Yeah, I started to work on it and got distracted, but was working on it
some more yesterday. As submitted, it leaks PGresults, and makes some
inconsistent and mostly undocumented changes in the APIs of the psql
functions involved. But I'm pretty close to having something committable.

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers