Re: SSI patch version 14

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Jeff Davis" <pgsql(at)j-davis(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SSI patch version 14
Date: 2011-01-31 19:55:11
Message-ID: 4D46BF3F020000250003A04A@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jeff Davis <pgsql(at)j-davis(dot)com> wrote:

> I don't think this function really cares about the visibility with
> respect to the current snapshot, right?

What it cares about is whether some other particular top level
transaction wrote a tuple which we *would* read except that it is
not visible to us because that other top level transaction is
concurrent with ours. If so, we want to flag a read-write conflict
out from our transaction and in to that other transaction.

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-01-31 19:58:27 Re: Error code for "terminating connection due to conflict with recovery"
Previous Message Jeff Davis 2011-01-31 19:54:37 Re: SSI patch version 14