Closed barrelltech closed 3 weeks ago
🤔 Interesting, I wonder (just for debugging purposes) if making your test run synchronous (using use ExUnit.Case, async: false
) fixes the problem?
I also found this: https://stackoverflow.com/questions/19382284/postgresql-error-tuple-concurrently-updated
So maybe the error can have something to do with transactions or creating functions...
There's also this: https://dba.stackexchange.com/questions/160954/postgres-error-tuple-concurrently-updated
I can see that the error is coming from EctoWatch.WatcherServer.init
, so it's happening as the watcher is being created and I think in the CREATE OR REPLACE FUNCTION
call. I wonder if it's because a number of tests are trying to create functions at the same time. Maybe if this was inside a transaction (?)
I guess that this is solved in #14 / 0.7.0, but let me know if not
When running my tests, I'm periodically receiving the following error:
I have not looked into this yet, likely just have to turn off
EctoWatch
for tests. I'll try to report back with the solution when I have time to look into it! For now rerunning the tests works (fails ~1/5 times)