Hey, regarding the interactiveTransactions new amazing feature. In the release notes it states that you can control isolation level and locking for now, which is OK, but what is the current locking then? If I do to actions in the same transaction. Let’s say an aggregation on a table and then a query on the same table, can some other transaction insert or change data between my to reads?

I think you misread it. It doesn’t support it as of now:

@Ryan I read it ok. I understand it doesn’t support controlling it as of now. I can’t control it, but what is the current state…?

In the release notes it states that you can control isolation level and locking for now, which is OK

I guess it was a typo then in your message 🙂 As for the current state, the isolation level should be what the database has by default for transactions.

@Ryan Lol, yeah, typo. Should have been can’t (writing with a baby on your lap…). Could you assist in to what does that mean in postgres?

As per the docs Read committed should be the default:

@Ryan well this makes it useless for my case haha. Thanks though…!