| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Kevin Grittner <kgrittn(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Kyle Kingsbury <aphyr(at)jepsen(dot)io> |
| Subject: | Re: Potential G2-item cycles under serializable isolation |
| Date: | 2020-06-09 02:12:05 |
| Message-ID: | CAH2-WzmLkqYqaBBqjOgemVZQx9J9rzqswFRzuAuKhEAACmveeA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Jun 8, 2020 at 7:07 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> Right. I think that you can go ahead and change it without further input here.
Also, is it necessary to have the TransactionIdEquals() tests in both
HeapCheckForSerializableConflictOut() and
CheckForSerializableConflictOut()? Apart from anything else, the test
in HeapCheckForSerializableConflictOut() occurs before we establish
the topmost XID -- it could be a subxid, in which case the test is
wrong. Though it doesn't actually matter on account of the redundancy,
IIUC.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2020-06-09 02:17:06 | Re: Potential G2-item cycles under serializable isolation |
| Previous Message | Peter Geoghegan | 2020-06-09 02:07:46 | Re: Potential G2-item cycles under serializable isolation |