Re: [PATCHES] Current-stream read for psql's \copy - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCHES] Current-stream read for psql's \copy
Date
Msg-id 15317.1076428541@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCHES] Current-stream read for psql's \copy  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: [PATCHES] Current-stream read for psql's \copy  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.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


pgsql-hackers by date:

Previous
From: "Keith Bottner"
Date:
Subject: Re: MS SQL features for new version
Next
From: Bruce Momjian
Date:
Subject: Re: PQinSend question