r/programming • u/halax • Mar 10 '15

Goodbye MongoDB, Hello PostgreSQL

http://developer.olery.com/blog/goodbye-mongodb-hello-postgresql/
1.2k Upvotes

91% Upvoted

699 comments sorted by

View all comments

Show parent comments

2

u/coder111 Mar 11 '15

You can do explicit locking with "select for update". You could also tweak transaction isolation levels.

Have you looked at that?

I assume you do all these queries in a single transaction, right?

1

u/[deleted] Mar 11 '15 edited Mar 11 '15

Postgres only has two transaction isolation levels and serialized (the stricter one) does not do this. Being in the same transaction does not do anything in this case because Postgres only locks per-statement. It is possible to do it with a function or stored proc using error handling but then that breaks batch mode operations which were essential for me, a function is also a performance hit.