X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by postgresql.org (Postfix) with ESMTP id CA7BE9DC9A5
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Mon, 19 Dec 2005 09:26:11 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 37372-04
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Mon, 19 Dec 2005 09:26:02 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from matrix.gatewaynet.com (host2.dynacom.ondsl.gr [62.103.35.210])
	by postgresql.org (Postfix) with ESMTP id 4A8889DC9AC
	for <pgsql-sql@postgresql.org>; Mon, 19 Dec 2005 09:25:53 -0400 (AST)
Received: from matrix.gatewaynet.com (localhost.localdomain [127.0.0.1])
	by matrix.gatewaynet.com (8.12.8/8.12.8) with ESMTP id jBJEPDOp007937;
	Mon, 19 Dec 2005 16:25:13 +0200
Received: from localhost (achill@localhost)
	by matrix.gatewaynet.com (8.12.8/8.12.8/Submit) with ESMTP id
	jBJEPD40007933; Mon, 19 Dec 2005 16:25:13 +0200
Date: Mon, 19 Dec 2005 16:25:13 +0200 (EET)
From: Achilleus Mantzios <achill@matrix.gatewaynet.com>
To: Lane Van Ingen <lvaningen@esncc.com>
cc: pgsql-sql@postgresql.org
Subject: Re: How to Force Transactions to Process Serially on A Table
In-Reply-To: <EKEMKEFLOMKDDLIALABICEGLCGAA.lvaningen@esncc.com>
Message-ID: <Pine.LNX.4.44.0512191615510.7853-100000@matrix.gatewaynet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-7
Content-Transfer-Encoding: 8BIT
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0 required=5 tests=[none]
X-Spam-Score: 0
X-Spam-Level: 
X-Archive-Number: 200512/157
X-Sequence-Number: 23699

O Lane Van Ingen έγραψε στις Dec 19, 2005 :

> I am using PL/SQL functions on Windows 2003, version 8.0.1.
> 
> I have not used explicit PostgreSQL LOCKing before, but I need some advice
> on how properly to use some explicit locking. I think that duplicate key
> violations I am now getting are the result.
> 
> I want to force transactions being used to update a table to be processed on
> a first-come, first-served basis. I want my Pl/sql function to execute to
> completion on each transaction before another starts.
> 
> Need some advice on how to do this. From what I can read in the docs, it
> looks like I need to solve the problem by using the following, but doing so
> gives me an SPI_execution error:
>   BEGIN;
>   LOCK <table> IN SHARE ROW  EXCLUSIVE MODE;
>     lock adns_report_hour_history in share row exclusive mode;
>   INSERT INTO <table> VALUES ...  - or - UPDATE <table> SET ....
>   COMMIT;
> Will this make the next transaction wait until the previous transaction has
> completed? Do I need to set any config parameters?
> 
> If you can include an actual code snippet in the response, it would help ...

what you want is to set the xaction isolation level.

BEGIN;
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE;
......
COMMIT;

Be prepared for serialization failures though.

> 
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
> 

-- 
-Achilleus