Received: from isti.hvi.net (root@isti.hvi.net [208.219.108.244]) by hub.org (8.8.8/8.8.8) with ESMTP id NAA01924; Tue, 20 Oct 1998 13:00:31 -0400 (EDT) (envelope-from p.friberg@isti.com) Received: from isti.com (localhost [127.0.0.1]) by isti.hvi.net (8.8.5/8.8.5) with ESMTP id JAA02893; Mon, 19 Oct 1998 09:03:39 -0400 Sender: paulf@isti.hvi.net Message-ID: <362B38AB.BCFFE717@isti.com> Date: Mon, 19 Oct 1998 09:03:39 -0400 From: Paul Friberg CEO - ISTI Organization: ISTI X-Mailer: Mozilla 4.03 [en] (X11; I; Linux 2.0.30 i586) MIME-Version: 1.0 To: pgsql-sql@postgresql.org, pgsql-hackers@postgresql.org Subject: PostgreSQL COPY command Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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