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

BUG #6269: Anomaly detection

From: "Paul Stapersma" <paul(dot)stapersma(at)gmail(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #6269: Anomaly detection
Date: 2011-10-25 09:51:32
Message-ID: 201110250951.p9P9pWb5014484@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      6269
Logged by:          Paul Stapersma
Email address:      paul(dot)stapersma(at)gmail(dot)com
PostgreSQL version: 8.3.3
Operating system:   Mac OS X Version 10.6.8
Description:        Anomaly detection
Details: 

Dear reader,

For a project at my University, we compared PostgreSQL with MySQL's InnoDB.
In this research, we found several cases in which anomalies where detected
in Isolation levels that guaranteed not to have these anomalies.

In short summary:
- we detected non-repeatable reads in the repeatable read isolation level
- we detected non-repeatable reads in the serializable isolation level
- we detected phantoms in the serializable isolation level
- we detected lost updates in the repeatable read isolation level
- we detected lost updates in the serializable isolation level

Furthermore, we detected differences between Read Committed and Read
Uncommitted and differences between Serializable and Repeatable Read which
is in contrast to the documentation.

A full report on our findings can be found here:
http://dl.dropbox.com/u/19316575/report.pdf

Friendly regards,

Paul Stapersma

Responses

pgsql-bugs by date

Next:From: Magnus HaganderDate: 2011-10-25 12:39:22
Subject: Re: BUG #6264: Superuser does not have inherent Replication permission
Previous:From: John R PierceDate: 2011-10-25 09:09:52
Subject: Re: BUG #6266: Create temp tables on Slave

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