Re: Potential G2-item cycles under serializable isolation - Mailing list pgsql-bugs

From Kyle Kingsbury
Subject Re: Potential G2-item cycles under serializable isolation
Date
Msg-id 4790f8af-91ce-1b2d-3c3e-4f2662c20b7a@jepsen.io
Whole thread Raw
In response to Re: Potential G2-item cycles under serializable isolation  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-bugs
On 6/2/20 7:13 PM, Thomas Munro wrote:
> That's (unfortunately) a known problem under concurrency.  It'd be
> very nice to fix that, but it's an independent problem relating to DDL
> (not just tables, and not just IF EXISTS DDL, but anything modifying
> catalogues can race in this way and miss out on "nice" error messages
> or the IF EXISTS no-op).  Here's a good short summary:

Ah, yes, this does explain it, thank you! I was a bit concerned, because I know 
Postgres has a reputation for having transactional DDL. I guess this part of the 
API isn't. :)

--Kyle




pgsql-bugs by date:

Previous
From: Kyle Kingsbury
Date:
Subject: Re: Potential G2-item cycles under serializable isolation
Next
From: Kyle Kingsbury
Date:
Subject: Re: Potential G2-item cycles under serializable isolation