| From: | Kyle Kingsbury <aphyr(at)jepsen(dot)io> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, 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> |
| Subject: | Re: Potential G2-item cycles under serializable isolation |
| Date: | 2020-06-15 12:42:38 |
| Message-ID: | 1fbd7c3d-f3e3-a14f-d391-d7c4b490e977@jepsen.io |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 6/14/20 9:30 PM, Thomas Munro wrote:
> By my reading of their manual, MySQL (assuming InnoDB) uses SI for
> REPEATABLE READ just like us, and it's also their default level.
>
> https://dev.mysql.com/doc/refman/8.0/en/innodb-consistent-read.html
That can't be right. MySQL repeatable read allows lost update, write skew, and
at least some kinds of read skew: it's got to be weaker than SI and also weaker
than RR. I think it's actually Monotonic Atomic View plus some read-only
constraints?
https://github.com/ept/hermitage
<sigh> I really gotta do a report on MySQL too...
--Kyle
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2020-06-15 14:45:19 | Re: BUG #16492: DROP VIEW IF EXISTS error |
| Previous Message | Daniel Verite | 2020-06-15 12:30:23 | Re: Potential G2-item cycles under serializable isolation |