From: | "alexandre :: aldeia digital" <alepaes(at)aldeiadigital(dot)com(dot)br> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Abort Transaction DP PK (again) |
Date: | 2003-08-08 20:22:26 |
Message-ID: | 4150.192.168.1.100.1060374146.squirrel@webmail.ad2.com.br |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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(at)postgresql(dot)org)
>
From | Date | Subject | |
---|---|---|---|
Next Message | Prasanth | 2003-08-08 21:01:30 | Re: Retrieving tuple data on insert |
Previous Message | Stef | 2003-08-08 17:45:50 | Re: Analyze makes queries slow... |