X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 9724ED1C9B4 for ; Fri, 8 Aug 2003 20:21:40 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 77113-02 for ; Fri, 8 Aug 2003 17:20:13 -0300 (ADT) Received: from spirit.aldeiadigital.com.br (unknown [200.225.213.137]) by svr1.postgresql.org (Postfix) with ESMTP id AD3A4D1C9A6 for ; Fri, 8 Aug 2003 17:21:24 -0300 (ADT) Received: from webmail.ad2.com.br (localhost.localdomain [127.0.0.1]) by spirit.aldeiadigital.com.br (8.11.6/8.11.6) with SMTP id h78KMPq25757 for ; Fri, 8 Aug 2003 17:22:26 -0300 Received: from 192.168.1.100 (SquirrelMail authenticated user alepaes) by webmail.ad2.com.br with HTTP; Fri, 8 Aug 2003 17:22:26 -0300 (BRT) Message-ID: <4150.192.168.1.100.1060374146.squirrel@webmail.ad2.com.br> In-Reply-To: <200308080937.34002.josh@agliodbs.com> References: <1108.200.170.156.137.1060275870.squirrel@webmail.ad2.com.br> <200308080937.34002.josh@agliodbs.com> Date: Fri, 8 Aug 2003 17:22:26 -0300 (BRT) Subject: Re: Abort Transaction DP PK (again) From: "alexandre :: aldeia digital" To: pgsql-sql@postgresql.org User-Agent: SquirrelMail/1.4.0 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/78 X-Sequence-Number: 14694 Josh, Itīs very difficult to change the behaviour of a duplicate PK, from "error" to "warning"? Itīs possible, in a future release, to have an exception-handling for all client interfaces, like ODBC or JDBC? Thanks, Alexandre > Alexandre, > >> I know that this topic was discuted before but I like an alternative for >> my high load INSERT query. >> Why Postgres abort a transaction when find a duplicate PK ?!?! > > Postgres currently aborts a transaction upon *any* error condition, except > warnings. We do not, currently, have a exception-handling model for > procedure code. It's on the TODO list. > > -- > Josh Berkus > Aglio Database Solutions > San Francisco > > ---------------------------(end of broadcast)--------------------------- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to majordomo@postgresql.org) >