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

From Bruce Momjian
Subject Re: [PATCHES] Current-stream read for psql's \copy
Date
Msg-id 200402102135.i1ALZKp21462@candle.pha.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 wrote:
> 
> What do people want to do with the current \copy behavior for stdin? 
> Right now if you supply a file name with queries using psql -f, the copy
> input is read from the terminal, not from the file.

Actually, I was wrong.  Right now \copy reads from psql's stdin, not
always the terminal.  It doesn't read from the same descriptor it gets
its SQL commands, unless they are the same as psql's stdin, like:
psql test < commands.sql

You could make STDIN be the command stream, and add 'psqlstdin' for
psql's stdin, but it seems like a very little used feature.  It doesn't
seem worth documenting it, let alone adding code to allow it.

I assume \copy is designed primarily to allow reading from _local_ files
rather than only files that exist on the database server, as COPY
requires.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [PATCHES] Current-stream read for psql's \copy
Next
From: Robert Treat
Date:
Subject: Re: MS SQL features for new version