Postgres transaction isolation level
See original GitHub issueHi,
Probably I’m missing something but I couldn’t find a way to specify transaction isolation level for Postgres (default to Read committed
which is not sufficient for my use case - in which Repeatable read
is needed).
Any way to workaround it (without changing postgres config or manually open transaction)?
Thanks a lot!
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Documentation: 15: 13.2. Transaction Isolation - PostgreSQL
The Serializable isolation level provides the strictest transaction isolation. This level emulates serial transaction execution for all committed transactions; ...
Read more >Transaction Isolation Levels With PostgreSQL as an example
Transaction Isolation Levels With PostgreSQL as an example · Dirty Read. Dirty read means read uncommitted changes of other transactions. · Lost Update...
Read more >Transaction Isolation in PostgreSQL - pgDash
Every transaction has it's isolation level set to one of these when it is created. The default level is “read committed”. Note that...
Read more >PostgreSQL Concurrency: Isolation and Locking
The SQL standard defines four levels of transaction isolation. The most strict is Serializable, which is defined by the standard in a ...
Read more >Transaction Isolation in Postgres | by Dhruv Arora - Medium
The four levels are Read uncommitted, read committed, repeatable read and serializable. Courtesy: Postgres official docs. The default isolation ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
OK. Thanks again.
In case someone else will encounter this thread - another possible option (which i didn’t try) is to use raw
SET TRANSACTION
statement which should be ran before any other query in the transaction.Something like this?