New answers tagged concurrency
This is how Postgres was designed from ground up (as opposed to SQL Server where this was added very late) See the manual for details: http://www.postgresql.org/docs/current/static/mvcc-intro.html You can't actually configure Postgres so that readers would block writers (automatically or implicitly) The only way to block read access in Postgres is to ...
Check with the business team to see if you can restructure the business process so that you can start and comit a new transaction for each row in the excel file. If anything failed, record the fail rows so that they would know which row was successful and which one failed
Top 50 recent answers are included