| From: | Amit Kapila <amit(dot)kapila(at)huawei(dot)com> |
|---|---|
| To: | "'Etsuro Fujita'" <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, "'pgsql-hackers'" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: A question about the psql \copy command |
| Date: | 2013-02-15 06:46:27 |
| Message-ID: | 008901ce0b48$2e742ec0$8b5c8c40$@kapila@huawei.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thursday, February 07, 2013 6:15 PM Etsuro Fujita wrote:
> Through the work on the patch [1], I had a question about the psql
> \copy command. We are permitted 1) but not permitted 2):
> 1) \copy foo from stdin ;
> 2) \copy foo from stdin;
> Is this intentional? I think it would be better to allow for 2).
> Attached is a patch.
Verified that attached patch resolves the problem mentioned by you.
Ran the regression to ensure that it should not break any existing syntax.
Although this is minor bug, but IMO it will improve consistency among \
commands, because other works fine with ";"
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro HORIGUCHI | 2013-02-15 08:32:43 | Re: Identity projection |
| Previous Message | Pavan Deolasee | 2013-02-15 06:42:39 | Re: I think we need PRE_COMMIT events for (Sub)XactCallbacks |