You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Prevent other threads from modifying the tables we're deleting from
* Used read_committed since it's the lowest level that works
* Tested various isolations:
* read_uncommitted - works, but PG treats it as read_committed[1]
* read_committed - works
* repeatable_read - skipped
* serializable - works (highest isolation level)
* Don't allow changes to table_max_id_cache by other threads while we're
accessing it
[1] https://www.postgresql.org/docs/13/transaction-iso.html
"In PostgreSQL, you can request any of the four standard transaction isolation
levels, but internally only three distinct isolation levels are implemented,
i.e., PostgreSQL's Read Uncommitted mode behaves like Read Committed. This is
because it is the only sensible way to map the standard isolation levels to
PostgreSQL's multiversion concurrency control architecture."
0 commit comments