Thread: psql reading from stdin

Hi

I was trying to populate the database in Windows by doing psql -f dumpfile.
It creates the tables just fine and executes the SET commands in the file,
but it ignores all the data given as COPY xxxx (xxx,xxx,xxx) FROM stdin;
commands.

\i dumpfile at the psql prompt also doesn't work.

To work around this, the dump file can be generated with pg_dump -D, meaning
store the data as INSERT commands rather than COPY.  But something is
apparently wrong with the stdin of psql in Windows.

Eric Rosenquist wrote:

>Hi
>
>I was trying to populate the database in Windows by doing psql -f dumpfile.
>It creates the tables just fine and executes the SET commands in the file,
>but it ignores all the data given as COPY xxxx (xxx,xxx,xxx) FROM stdin;
>commands.
>
>\i dumpfile at the psql prompt also doesn't work.
>
>To work around this, the dump file can be generated with pg_dump -D, meaning
>store the data as INSERT commands rather than COPY.  But something is
>apparently wrong with the stdin of psql in Windows.
>
>
>
>

This is probably the problem that we patched a couple of days ago.
Please see if converting the dump file to have unix line endings (NL
instead of CRNL) makes any difference. Alternatively, if you can compile
yourself, try with cvs tip.

cheers

andrew

Sure enough, COPY FROM stdin does work if the CRNL pairs are replaced with
NLs.  This is true for \i dumpfile and -f dumpfile.

----- Original Message -----
From: "Andrew Dunstan" <andrew@dunslane.net>
To: "Eric Rosenquist" <rosenquist@mail.utexas.edu>
Cc: <pgsql-hackers-win32@postgresql.org>
Sent: Monday, August 16, 2004 9:59 AM
Subject: Re: [pgsql-hackers-win32] psql reading from stdin


>
>
> Eric Rosenquist wrote:
>
> >Hi
> >
> >I was trying to populate the database in Windows by doing psql -f
dumpfile.
> >It creates the tables just fine and executes the SET commands in the
file,
> >but it ignores all the data given as COPY xxxx (xxx,xxx,xxx) FROM stdin;
> >commands.
> >
> >\i dumpfile at the psql prompt also doesn't work.
> >
> >To work around this, the dump file can be generated with pg_dump -D,
meaning
> >store the data as INSERT commands rather than COPY.  But something is
> >apparently wrong with the stdin of psql in Windows.
> >
> >
> >
> >
>
> This is probably the problem that we patched a couple of days ago.
> Please see if converting the dump file to have unix line endings (NL
> instead of CRNL) makes any difference. Alternatively, if you can compile
> yourself, try with cvs tip.
>
> cheers
>
> andrew
>