CORE-19229 - Remove transactions from StateManager read operations. #5401
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
driessamyn
changed the title
|
|
Jenkins build for PR 5401 build 1 Build Successful: |
driessamyn
changed the title
There was a problem hiding this comment.
First of all, whether a read operation executes within an explicit transaction or not, it still runs within a transaction context. The database implicitly starts a transaction for each statement, even if it's not explicitly wrapped in a BEGIN and COMMIT block. This is a standard behavior in PostgreSQL (PostgreSQL Transactions Documentation).
Secondly, regarding the default isolation level, our specification in Corda is set to Read Committed ( Corda Runtime OS - TransactionIsolationLevel.kt). This matches the default isolation level of PostgreSQL, which is also Read Committed. Therefore, from a data integrity perspective, using the default settings does not compromise the data integrity here.
Regarding the intention to remove the transaction for the read operation, using use { ... } might indeed be more efficient and simpler, potentially leading to some performance gains. While the impact might be minimal for a few statements, it could be more measurable for a large number of select queries.
No description provided.