X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id C2093D1D200 for ; Sun, 25 Jan 2004 21:09:20 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 66152-01 for ; Sun, 25 Jan 2004 17:08:51 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 8A577D1D1A4 for ; Sun, 25 Jan 2004 17:08:49 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id i0PL8nnX028574; Sun, 25 Jan 2004 16:08:49 -0500 (EST) To: Mauri Sahlberg Cc: "'pgsql-admin@postgresql.org'" Subject: Re: Procedures, triggers and transactions... In-reply-to: <1075062062.3217.29.camel@fault> References: <1075062062.3217.29.camel@fault> Comments: In-reply-to Mauri Sahlberg message dated "Sun, 25 Jan 2004 22:21:02 +0200" Date: Sun, 25 Jan 2004 16:08:49 -0500 Message-ID: <28573.1075064929@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/204 X-Sequence-Number: 12067 Mauri Sahlberg writes: > The framework is that a c++ application transforms xml-input data to > sql-procedure calls with appropriate parameters who in turn call another > procedures who in turn call another procedures... And as all procedures > are run in the transaction of the outermost select (in this case the c++ > application's select that called the initial procedure) we have huge > problems with concurrency. Why do you have "huge problems with concurrency"? Under MVCC the only reason for such things to conflict is if different transactions try to update the same rows. If you do have such updates, it would seem that breaking the transactions into smaller ones would be likely to introduce correctness issues ... regards, tom lane