Re: [JDBC] number of transactions doubling

From: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
To: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
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 08:56:15
Message-ID: 451CDFAF.5050804@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-jdbc

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.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Matthew T. O'Connor 2006-09-29 13:31:48 Re: autovacuum ignore tables
Previous Message Sriram Dandapani 2006-09-29 06:40:35 Re: autovacuum ignore tables

Browse pgsql-jdbc by date

  From Date Subject
Next Message Simon Riggs 2006-09-29 11:24:24 Re: Optimizations in the latest driver
Previous Message Jim C. Nasby 2006-09-29 00:47:36 Re: number of transactions doubling