| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Amit Khandekar <amit(dot)khandekar(at)enterprisedb(dot)com> |
| Cc: | Rajeev rastogi <rajeev(dot)rastogi(at)huawei(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: | 2013-11-20 12:41:19 |
| Message-ID: | CA+TgmoaCXXOJ18-CBZg0g7tvQmGy=-S2x_s9RkGmo3SQGu-Fqg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Nov 20, 2013 at 4:56 AM, Amit Khandekar
<amit(dot)khandekar(at)enterprisedb(dot)com> wrote:
> So I think it is best to solve this as a different issue, and we should ,
> for this commitfest, fix only COPY FROM. Once the \COPY existing issue is
> solved, only then we can start printing the \COPY TO status as well.
I actually think that we should probably fix the \COPY issue first.
Otherwise, we may end up (for example) changing COPY FROM in one
release and COPY TO in the next release, and that would be annoying.
It does cause application compatibility problems to some degree when
we change things like this, so it's useful to avoid doing it multiple
times. And I can't really see a principled reason for COPY FROM and
COPY TO to behave differently, either.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-11-20 12:52:58 | Re: additional json functionality |
| Previous Message | Amit Khandekar | 2013-11-20 12:31:43 | Re: COPY table FROM STDIN doesn't show count tag |