Re: psycopg concurrency control

On Sep 11, 2016, at 8:26 AM, John Lb <johnlb77@gmail.com> wrote:
> I am not a  Postgres guy  but  I tried to  read the  documentation and  I  believe that   Explicit Locking -->  Table
levelLocks -->  ROW EXCLUSIVE  are the way to go . 

You almost certainly *don't* have to do any explicit locking, even with writers to the same table; PostgreSQL will
largelyhandle the concurrency issues for you.  Note that once a particular connection has written to an (existing) row,
noother session can write to that same row until the first session commits or aborts; the second session will wait for
thefirst transaction to finish. 

--
-- Christophe Pettus
   xof@thebuild.com