> no locks in you backend PG is still handling the locks for you, so this isn’t like a bulletproof solution and - like always - depending on your use case, sca

> no locks in you backend PG is still handling the locks for you, so this isn’t like a bulletproof solution and - like always - depending on your use case, scale, etc this may or may not work. > No matter the load and concurrent users it will work like magic Postgres will buckle updating a single row at a certain scale. ————- Regardless, this article was about testing a type of scenario that is commonly not tested. You don’t always have a great tool like PG on hand that gives you solutions so this testing isn’t needed.