| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Panagiotis Pediaditis <pped(at)ics(dot)forth(dot)gr> |
| Cc: | Rodrigo De León <rdeleonp(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Locking entire database |
| Date: | 2007-09-14 14:50:52 |
| Message-ID: | 20070914145052.GC12432@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2007-09-14 15:16:44 | Re: Locking entire database |
| Previous Message | Sibte Abbas | 2007-09-14 14:48:05 | Re: Locking entire database |