Re: Deadlock with one table - PostgreSQL is doing it right

From: Hans Schou <hans(dot)schou(at)gmail(dot)com>
To: Rakesh Kumar <rakeshkumar464(at)mail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Deadlock with one table - PostgreSQL is doing it right
Date: 2017-12-22 08:05:57
Message-ID: CAApBw36dW+aD-wm96Z5A5p=Nx3sNHknaJ40E-LMWmtToBJW10A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2017-12-21 21:50 GMT+01:00 Rakesh Kumar <rakeshkumar464(at)mail(dot)com>:

> whenever SQLERROR EXIT ROLLBACK
>

Thanks. You are absolutely right.
After starting with:
WHENEVER SQLERROR EXIT ROLLBACK
the process getting the deadlock will exit to command prompt (with
%ERRORLEVEL% = 0).

So what actually found out was that Oracle has some strange combinations of
default values regarding
1. AUTOCOMMIT = 0
2. Don't exit/rollback on deadlock

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ertan Küçükoğlu 2017-12-22 10:21:04 Character with byte sequence error
Previous Message Ken Tanzer 2017-12-22 07:56:23 Re: Intersection or zero-column queries