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

From: hubert depesz lubaczewski <depesz(at)gmail(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Date: 2014-08-25 11:37:08
Message-ID: CAKrjmhcOjXMUHNB5_41_pAtcQ7_QZy+EXoBDdtDj1VU86Cafiw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Aug 22, 2014 at 6:55 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)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

In response to

Browse pgsql-general by date

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