Skip site navigation (1) Skip section navigation (2)

Re: [JDBC] number of transactions doubling

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: (view raw, whole thread or download thread mbox)
Lists: pgsql-adminpgsql-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      512.569.9461 (cell)

In response to

pgsql-admin by date

Next:From: Erik JonesDate: 2006-09-29 17:37:30
Subject: Re: [GENERAL] Array assignment behavior (was Re: Stored procedure
Previous:From: Paul B. AndersonDate: 2006-09-29 17:08:15
Subject: Re: Array assignment behavior (was Re: Stored procedure array

pgsql-jdbc by date

Next:From: Sriram DandapaniDate: 2006-09-29 18:31:11
Subject: Re: [JDBC] number of transactions doubling
Previous:From: Kris JurkaDate: 2006-09-29 16:47:41
Subject: Re: jdbc batch insert

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group