On Thu, May 7, 2009 at 6:13 PM, Simon Riggs si...@2ndquadrant.com wrote:
Apologies Michael, I see that my mail did remove you. That was a
unconscious error; I was particularly interested in your comments
regarding my assessment of the algorithmic complexity of the new theory
and existing
Greg Stark st...@enterprisedb.com wrote:
However on subsequent messages you attempted to re-add him but got
his email address wrong. I assume everyone else got a bounce like I
got?
Some of my emails are getting through; some not. I haven't figured
out why. I'm calling it best effort for
Greg Stark st...@enterprisedb.com wrote:
If I do something like SELECT count(*) FROM tab WHERE
complex_function(a,b) = 5
And then you INSERT INTO tab (a,b) VALUES (1,2). How would you
store any record of the fact that there's a serialization failure
iff complex_function(1,2)=5 in any way
On Thu, May 7, 2009 at 11:08 PM, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
I would assume that SELECT shown above would either resolve to a
table scan, in which case you would have to have an SIREAD lock at the
table level
That sounds like we're back to the MSSQL/Sybase way of doing
On Thu, 2009-05-07 at 22:47 +0100, Greg Stark wrote:
On Thu, May 7, 2009 at 6:13 PM, Simon Riggs si...@2ndquadrant.com wrote:
Apologies Michael, I see that my mail did remove you. That was a
unconscious error; I was particularly interested in your comments
regarding my assessment of the
On Tue, May 5, 2009 at 8:50 AM, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
While discussing potential changes to PostgreSQL documentation of
transaction isolation levels, Emmanuel Cecchet pointed out an
intriguing new paper[1] on a new algorithm to provide true
serializable behavior in
Neil Conway neil.con...@gmail.com wrote:
Tracking the read sets of each transaction would be very expensive.
Worse still, that information needs to be kept around after
end-of-transaction, which raises questions about where it should be
stored and how it should be cleaned up. Note that the
101 - 107 of 107 matches
Mail list logo
