From: | Jim Nasby <jim(at)nasby(dot)net> |
---|---|
To: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
Cc: | Sriram Dandapani <sdandapani(at)counterpane(dot)com>, pgsql-jdbc(at)postgresql(dot)org, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: [JDBC] number of transactions doubling |
Date: | 2006-09-29 17:21:52 |
Message-ID: | 932B486A-84EA-493E-A78E-6FB28871642F@nasby.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-jdbc |
On Sep 29, 2006, at 4:56 AM, Heikki Linnakangas wrote:
> Jim C. Nasby wrote:
>> On Thu, Sep 28, 2006 at 02:51:24PM -0700, Sriram Dandapani wrote:
>>
>>> The target table has triggers that route data to appropriate
>>> tables. The
>>> tables to which data is routed has check constraints that do further
>>> inserts. (All of this happens in 1 jdbc transaction)
>>>
>> Actually, no matter what JDBC is doing, all of that will happen
>> within a
>> single transaction on the database (unless you're using something
>> like
>> dblink from within the triggers). So even if you were issuing insert
>> statements with autocommit on, you'd see at most one transaction per
>> insert.
>>
>
> The triggers might use subtransactions. You get implicit
> subtransactions if have an EXCEPTION clause in a plpgsql function.
> I'm not sure if there's other things that do that as well.
Ahh, I thought that was handled within cmin/cmax.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
From | Date | Subject | |
---|---|---|---|
Next Message | Erik Jones | 2006-09-29 17:37:30 | Re: [GENERAL] Array assignment behavior (was Re: Stored procedure |
Previous Message | Paul B. Anderson | 2006-09-29 17:08:15 | Re: Array assignment behavior (was Re: Stored procedure array |
From | Date | Subject | |
---|---|---|---|
Next Message | Sriram Dandapani | 2006-09-29 18:31:11 | Re: [JDBC] number of transactions doubling |
Previous Message | Kris Jurka | 2006-09-29 16:47:41 | Re: jdbc batch insert |