Re: A question about the psql \copy command

From: Bruce Momjian <bruce(at)momjian(dot)us>
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-09-10 23:36:37
Message-ID: 20130910233637.GI16378@momjian.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 7, 2013 at 09:45:17PM +0900, 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.

Modified, attached patch applied. Thanks.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

Attachment Content-Type Size
copy.diff text/x-diff 1.0 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2013-09-11 00:14:10 Re: unaccent module - two params function should be immutable
Previous Message Bruce Momjian 2013-09-10 22:49:27 Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block