From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Brook Milligan <brook(at)biology(dot)nmsu(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] psql -f inconsistency with "copy from stdin" |
Date: | 2000-01-12 23:29:31 |
Message-ID: | Pine.LNX.4.21.0001122057120.1646-100000@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2000-01-12, Tom Lane mentioned:
> It seems to me that we ought to provide both behaviors, but make sure
> that the one that supports data-in-the-script is the one invoked by
> COPY FROM STDIN (since that's what pg_dump uses). Perhaps psql's \copy
> command can be set up to support the other alternative.
\copy from stdin is not used yet. That would work. There might be issues
I'm overlooking now, but anything else that came up in this thread will
most likely not work in the general case.
--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2000-01-12 23:29:36 | Re: Regress tests reveal *serious* psql bug |
Previous Message | Peter Eisentraut | 2000-01-12 23:29:25 | proposal -- Re: [HACKERS] Re: [SQL] createdb -D xxxx not working |