| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Mark Feit <mfeit+postgresql(at)notonthe(dot)net> |
| Subject: | Re: [PATCHES] Current-stream read for psql's \copy |
| Date: | 2004-02-10 15:55:41 |
| Message-ID: | 15317.1076428541@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom Lane wrote:
>> I propose we not break existing applications. If we change it the way
>> you suggest, there'll be no way to do the above.
> But does anyone use such a capability?
What, you're going to remove a feature because you don't think it's
used? We've been burnt by that approach before.
> The program has to generate \. to terminate the input
No it doesn't. EOF will do fine. The source program doesn't
necessarily have to know anything about COPY, as long as its output is
in a format COPY can cope with (eg, tab-delimited).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Gibson | 2004-02-10 16:44:02 | Re: [GENERAL] dblink - custom datatypes don't work |
| Previous Message | Rodrigo | 2004-02-10 15:23:06 | Re: MS SQL features for new version |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Goodwin | 2004-02-10 16:38:16 | Re: Patch to psql to allow SEARCH_PATH to be set from env |
| Previous Message | Tom Lane | 2004-02-10 15:30:08 | Re: Patch to psql to allow SEARCH_PATH to be set from env |