| From: | Dan Ports <drkp(at)csail(dot)mit(dot)edu> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: SSI atomic commit |
| Date: | 2011-07-07 21:21:59 |
| Message-ID: | 20110707212159.GF76634@csail.mit.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
This is not really a related issue, but Kevin and I found it while
looking into this issue, and it was included in the patch we sent out.
Dan
--
Dan R. K. Ports MIT CSAIL http://drkp.net/
| Attachment | Content-Type | Size |
|---|---|---|
| ssi-possibleconflict-test.patch | text/x-diff | 677 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2011-07-07 21:24:21 | Re: SSI atomic commit |
| Previous Message | Dan Ports | 2011-07-07 21:08:07 | Re: SSI atomic commit |