Support Transactions with different isolation levels

[jtaekema]

Postgres supports several isolation levels: see https://www.postgresql.org/docs/current/static/transaction-iso.html

• Read Uncommitted (internally the same as Read Committed)
• Read Committed (default)
• Repeatable Read
• Serializable

Some types of systems need the guarantees provided by the more strict isolation levels.

To get around this support I have been running a simple command to upgrade the transaction, but it would be nice if there was an easy way to start the transaction that way.

Like:

conn.BeginTransaction(IsolationLevel.RepeatableRead)

There are other options that would be useful for performance tuning, such as READ WRITE, READ ONLY, and [ NOT ] DEFERRABLE.

[johto]

To get around this support I have been running a simple command to upgrade the transaction, but it would be nice if there was an easy way to start the transaction that way.

Unfortunately I don't see how this could possibly work given that we have to work with the interface database/sql provides.

[msakrejda]

I agree--I think the limited database/sql API ties our hands here. Do you have a concrete suggestion as to how to approach this?

[itsjamie]

This issue should be able to be fixed with the introduction of IsolationLevels to database/sql with 1.8 assuming enough implementation happens with #531 for it not to be pulled.

[ThomasHabets]

This is in 1.8 and lack of it is preventing me from cleaning up code manually setting isolation level inside every transaction.

[mattyw]

Has this not been fixed now that ed1a26d has landed?

[ThomasHabets]

I can confirm that it works perfectly for me.