PostgreSQL COPY command - Mailing list pgsql-hackers

From Paul Friberg CEO - ISTI
Subject PostgreSQL COPY command
Date
Msg-id 362B38AB.BCFFE717@isti.com
Whole thread Raw
List pgsql-hackers
Hi all,

Does anyone know if there are plans to upgrade the
COPY command so it spits back some intelligent results
when it finishes. At the present time if it finds a bad
row or a non-unique key set, it simply quits out with a
statement:

    "resetting connection"

Which is not very informative. Let me know if this part of
the code needs working on. If nobody else is adding this,
I would be happy to dive in.

I could imagine this spitting out a message about a certain
line not passing muster, or even the total number of rows
in the file input/output being listed (as is now returned
with the INSERT/DELETE/UPDATE/SELECT commands).


Cheers,

Paul
--
 Paul Friberg - p.friberg@isti.com - http://www.isti.com
      (914) 256-9290 Office - (914) 256-9299 FAX
    ISTI==Instrumental Software Technologies, Inc.
Systems Integration and Software Development Specialists

pgsql-hackers by date:

Previous
From: jwieck@debis.com (Jan Wieck)
Date:
Subject: Re: [HACKERS] What about LIMIT in SELECT ?
Next
From: darcy@druid.net (D'Arcy J.M. Cain)
Date:
Subject: Re: [HACKERS] Re: inet/cidr/bind