Re: SSI atomic commit - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: SSI atomic commit
Date
Msg-id 4E162628.6080100@enterprisedb.com
Whole thread Raw
In response to Re: SSI atomic commit  (Dan Ports <drkp@csail.mit.edu>)
Responses Re: SSI atomic commit
List pgsql-hackers
On 08.07.2011 00:21, Dan Ports wrote:
> We should also apply the attached patch, which corrects a minor issue
> with the conditions for flagging transactions that could potentially
> make a snapshot unsafe.
>
> There's a small window wherein a transaction is committed but not yet
> on the finished list, and we shouldn't flag it as a potential conflict
> if so. We can also skip adding a doomed transaction to the list of
> possible conflicts because we know it won't commit.

Hmm, it's now also possible for the transaction to be prepared, and 
already visible to others, but not yet flagged as committed. Shouldn't 
those be included too?

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Cédric Villemain
Date:
Subject: Re: Re: patch review : Add ability to constrain backend temporary file space
Next
From: Alvaro Herrera
Date:
Subject: cataloguing NOT NULL constraints