Re: SSI atomic commit

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Dan Ports" <drkp(at)csail(dot)mit(dot)edu>, "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SSI atomic commit
Date: 2011-07-07 21:24:21
Message-ID: 4E15DDB5020000250003F0A5@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dan Ports <drkp(at)csail(dot)mit(dot)edu> 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.
>
> 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.

Agreed -- that was in the SSI atomic commit patch, but probably
should have been submitted separately. The issue is really
orthogonal -- it's just that we found it while looking at the other
race condition.

-Kevin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Cédric Villemain 2011-07-07 21:26:31 Re: Re: patch review : Add ability to constrain backend temporary file space
Previous Message Dan Ports 2011-07-07 21:21:59 Re: SSI atomic commit