Re: [ADMIN] number of transactions doubling - Mailing list pgsql-jdbc

From Jim Nasby
Subject Re: [ADMIN] number of transactions doubling
Date
Msg-id 932B486A-84EA-493E-A78E-6FB28871642F@nasby.net
Whole thread Raw
In response to Re: [ADMIN] number of transactions doubling  (Heikki Linnakangas <heikki@enterprisedb.com>)
List 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@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)



pgsql-jdbc by date:

Previous
From: Kris Jurka
Date:
Subject: Re: jdbc batch insert
Next
From: "Sriram Dandapani"
Date:
Subject: Re: [ADMIN] number of transactions doubling