Transaction not respecting locks
using supabase and postgres
spam the above function, sometimes kat gets created more than once
however adding trx.execute(BEGIN TRANSACTION ) and then manually comitting it solves the problem, but drizzle logs gives an warning that a transaction is ongoing