Atomicity in DB transactions (Rollback related)

From: "Jasbinder Singh Bali" <jsbali(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Atomicity in DB transactions (Rollback related)
Date: 2007-06-18 15:45:17
Message-ID: a47902760706180845s4fea3f43w489c757bc4999b10@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,
I have a Pl/Perlu function in which I have a statement like this:

*******************
my $query_tbl_l_header = $dbh->prepare("SELECT
sp_insert_tbl_l_header(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)");

my $exec_l_from
=$query_tbl_l_header->execute($unmask_id,$from,$to,$sender,$subject,$replyto,$cc,$bcc,$messageid,$inreplyto,$reference,$mversion,$con_type,$con_id,$con_des,$con_enc,$con_length,$con_dis);
*******************

even if this execute, that calls a function sp_insert_tbl_l_header, fails,
subsequent trasactions continue without failing the whole perl function
there and then and makes the Db inconsistent.
Shouldn't the whole function fail and exit at that particular failure and
don't continue?
Please let me know how do these transactions work in postgres.

Thanks,
Jas

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Francisco Reyes 2007-06-18 15:51:15 Re: pg_restore out of memory
Previous Message Alvaro Herrera 2007-06-18 15:43:17 Re: Apparent Wraparound?