| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: A question about the psql \copy command |
| Date: | 2013-02-10 20:34:49 |
| Message-ID: | CA+TgmobTXoCxC+-mE6XSPnTOCeo-AefS-yv2SvBjYxi6bFthOg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Feb 7, 2013 at 7:45 AM, Etsuro Fujita
<fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> 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.
Sounds reasonable to me.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-02-10 20:53:42 | Re: backup.sgml patch that adds information on custom format backups |
| Previous Message | David Fetter | 2013-02-10 15:39:26 | Re: Department of Redundancy Department: makeNode(FuncCall) division |