Re: deadlock in single-row select-for-update + update scenario? How could it happen? - Mailing list pgsql-general

From hubert depesz lubaczewski
Subject Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Date
Msg-id CAKrjmhcOjXMUHNB5_41_pAtcQ7_QZy+EXoBDdtDj1VU86Cafiw@mail.gmail.com
Whole thread Raw
In response to Re: deadlock in single-row select-for-update + update scenario? How could it happen?  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-general
On Fri, Aug 22, 2014 at 6:55 PM, Jeff Janes <jeff.janes@gmail.com> wrote:
What transaction isolation level is being used?

Sorry for late reply - the user was away for parts of friday, I was away on weekend, and just now got answer - it's read committed.

depesz

pgsql-general by date:

Previous
From: hubert depesz lubaczewski
Date:
Subject: Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Next
From: Michael Paquier
Date:
Subject: Re: Way to identify the current session's temp tables within pg_class ?