| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Amit Khandekar <amit(dot)khandekar(at)enterprisedb(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, 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-21 04:43:19 |
| Message-ID: | 7542.1385008999@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Amit Khandekar <amit(dot)khandekar(at)enterprisedb(dot)com> writes:
> Rather than a behaviour change, it is a bug that we are fixing. User
> already expects to see copy status printed, so as per user there would be
> no behaviour change.
This is arrant nonsense. It's a behavior change. You can't make it
not that by claiming something about user expectations. Especially
since this isn't exactly a corner case that nobody has seen in
the fifteen years or so that it's worked like that. People do know
how this works.
I don't object to changing it, but I do agree with Robert that it's
important to quantize such changes, ie, try to get a set of related
changes to appear in the same release. People don't like repeatedly
revising their code for such things.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | firoz e v | 2013-11-21 05:23:41 | Re: [PoC] pgstattuple2: block sampling to reduce physical read |
| Previous Message | Amit Kapila | 2013-11-21 04:20:23 | Re: Extra functionality to createuser |