Search Postgresql Archives

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: deadlock in single-row select-for-update + update scenario? How could it happen?
From: hubert depesz lubaczewski <depesz@xxxxxxxxx>
Date: Mon, 25 Aug 2014 13:37:08 +0200
Cc: pgsql-general <pgsql-general@xxxxxxxxxxxxxx>
In-reply-to: <CAMkU=1y5honjR=VPpsnaY1ZsJRwAsChj=CCu-zhv3ZRHMeWX1A@mail.gmail.com>

On Fri, Aug 22, 2014 at 6:55 PM, Jeff Janes <jeff.janes@xxxxxxxxx> 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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- deadlock in single-row select-for-update + update scenario? How could it happen?
  - From: hubert depesz lubaczewski
- Re: deadlock in single-row select-for-update + update scenario? How could it happen?
  - From: Jeff Janes

Prev by Date: Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Next by Date: Re: Way to identify the current session's temp tables within pg_class ?
Previous by thread: Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Next by thread: Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux