From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(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:16:14 |
Message-ID: | 200402101516.i1AFGE119346@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > 'psql test </tmp/x' works fine, but 'psql -f /tmp/x test' hangs waiting
> > for input from stdin. Why would we want STDIN to read from the terminal
> > if all commands are being read from a file with -f?
>
> Actually, that behavior is extremely useful. Consider
> program-that-generates-data | psql -f somescript
> The script can issue a COPY FROM STDIN to insert the data coming through
> the pipe.
>
> > I propose we just fix this and document it in the release notes.
>
> 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? The program has to generate \.
to terminate the input, so why not have it issue the \copy too? Seems
cleaner.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-02-10 15:20:59 | Re: PQinSend question |
Previous Message | Keith Bottner | 2004-02-10 15:15:07 | Re: MS SQL features for new version |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-02-10 15:30:08 | Re: Patch to psql to allow SEARCH_PATH to be set from env |
Previous Message | Tom Lane | 2004-02-10 15:10:22 | Re: [PATCHES] Current-stream read for psql's \copy |