3 ms·
Whatever transaction isolation issues PostgreSQL might have, I guarantee you it doesn't have the "same lame" ones as MySQL. As just one example: "range locking
by rosser 11y ago
Whatever transaction isolation issues PostgreSQL might have, I guarantee you it doesn't have the "same lame" ones as MySQL.
As just one example: "range locking". Look it up.
- TheOsiris 11y agothe biggest one for me is the lack of support for nested transactions
- rosser 11y agoWhich you can effectively accomplish in PostgreSQL with SAVEPOINTs. In fact, with those, you can have arbitrarily complicated nesting of "transactions", though that does start to smell a bit like a foot-gun pretty quickly. http://www.postgresql.org/docs/current/static/sql-savepoint.html http://www.postgresql.org/docs/current/static/sql-savepoint....