Skip site navigation (1) Skip section navigation (2)

Isolation Levels (Re: show stopper)

From: Zeugswetter Andreas DBT <Andreas(dot)Zeugswetter(at)telecom(dot)at>
To: "'pgsql-hackers(at)hub(dot)org'" <pgsql-hackers(at)hub(dot)org>
Subject: Isolation Levels (Re: show stopper)
Date: 1998-01-26 10:14:49
Message-ID: 219F68D65015D011A8E000006F8590C6010A51A6@sdexcsrv1.sd.spardat.at (view raw or flat)
Thread:
Lists: pgsql-hackers
Hi all,

I have been scanning the thread from Jan Vicherek who is having heavy
browsing activity blocking updates.

Basically there should be no need for read locks in postgresql,
since the before images are in the table until the next vacuum.
Therefore a scheme could be implemented, where readers
always read data as it was at the time of their begin work statement.
(The Oracle way)

An other alternative would be to implement a:
set isolation to {dirty|uncommited} read; 
This enables readers  willing to take the risc of reading uncommitted
data 
to read without a read lock. This is often very useful. (The Informix
and DB/2 way)

In the long run I think one of the above should be implemented (I prefer
the second,
as it is less resource consuming, and easier to handle (e.g. with
indexes)).

Andreas

pgsql-hackers by date

Next:From: Andrew MartinDate: 1998-01-26 10:31:19
Subject: Re: [HACKERS] Re: Copyright question: GPL patches for non-GPL packages (fwd)
Previous:From: Edwin S. RamirezDate: 1998-01-26 09:08:25
Subject: Problem with initdb in lastest Snapshot

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group