The birth of the open source enterprise stack
Posted Jul 7, 2006 0:38 UTC (Fri) by nix
In reply to: The birth of the open source enterprise stack
Parent article: The birth of the open source enterprise stack
The PostgreSQL manual makes the point that perfect isolation isn't possible without giving the database what amounts to a theorem prover *and* complete knowledge of your app's control flow
I'm curious what you're talking about, because I can't find anything like that in the PostgreSQL manual. I think perfect isolation is straightforward using read and write logs, and that PostgreSQL does exactly that. What am I missing?
See section 184.108.40.206
of the PostgreSQL manual, and the discussion of predicate locking. (Note, when it says `the details of every query', it means the details
. In the presence of random-access cursors I suspect this reduces to solving the halting problem.)
But what do you mean about transactions going read-only?
If you turn on serializable isolation in some transaction in said expensive proprietary RDBMS, you can no longer carry out INSERTs or UPDATEs in that transaction. It makes it really very
to post comments)