Received: from downtown.oche.de (root@downtown.oche.de [194.94.253.3]) by hub.org (8.9.3/8.9.3) with ESMTP id CAA22912 for ; Thu, 2 Sep 1999 02:14:54 -0400 (EDT) (envelope-from darwin!mne.de!lists@downtown.oche.de) Received: from darwin.UUCP (uucp@localhost) by downtown.oche.de (8.9.3/8.9.3/Debian/GNU) with UUCP id IAA03270 for postgreSQL.org!pgsql-sql; Thu, 2 Sep 1999 08:10:06 +0200 Received: from darwin.oche.de (really [127.0.0.1]) by darwin.oche.de via in.smtpd with smtp id (Debian Smail3.2.0.101) for pgsql-sql@postgreSQL.org; Thu, 2 Sep 1999 08:04:24 +0200 (CEST) Message-Id: Date: Thu, 2 Sep 1999 08:04:24 +0200 (CEST) From: Martin Neumann To: pgsql-sql@postgreSQL.org Every day I get a plain-vanilla ASCII-file containg space-separated values. I parse the file with a script and make each row in the file an INSERT-statement. Sometimes one of these many statements contains rubbish becaused the line in the file I was processing contained rubbish. If I did a separate transaction for every INSERT-statement this doesn't hurt because only one statement (the broken one) doesn't get processed. But I have to do about 100.000 INSERTs everyday and this is _slow_ if I let PostgreSQL process each statement individually. So my idea was to use a chained transaction. This works perfectly as long as all INSERT-statement are okay. But if one is broken, PostgreSQL doesn't process the other statements, too. My goal is to use chained transaction and to don't have to bother about broken INSERT-statements. Is that possible or to do I have to check the statements manually (by the script) before executing? -- `Unser Kopf ist rund, damit das Denken die Richtung wechseln kann.' ~ Francis Picabia