Re: Locking entire database - Mailing list pgsql-general

From Martijn van Oosterhout
Subject Re: Locking entire database
Date
Msg-id 20070914145052.GC12432@svana.org
Whole thread Raw
In response to Re: Locking entire database  (Panagiotis Pediaditis <pped@ics.forth.gr>)
List pgsql-general
On Fri, Sep 14, 2007 at 05:45:07PM +0300, Panagiotis Pediaditis wrote:
> Well the problem is I am working on rdf query engine for persistent RDF
> data. The data is stored/structured in a specific way in the database.
> When i perform updates in parallel, because there are cross table
> dependencies, I end up with inconsistencies, For example One transaction
> reads to see if there is a resource so as to add a property where it is
> a subject. Then an other transaction deletes the resource after the
> first has decided that the resource is there but before it added the
> property.

Sounds like what you need is serializable transactions. Then the server
will tell you if something conflicts.

Have a ncie day,
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

Attachment

pgsql-general by date:

Previous
From: "Sibte Abbas"
Date:
Subject: Re: Locking entire database
Next
From: Thomas Kellerer
Date:
Subject: Re: Locking entire database